On 2/18/25 6:48 PM, Alejandro Colomar wrote: > On Tue, Feb 18, 2025 at 06:33:26PM -0500, Carlos O'Donell wrote: >> On 2/17/25 11:51 AM, Askar Safin wrote: >>> Signed-off-by: Askar Safin <safinaskar@xxxxxxxxxxxx> >> >> LGTM. >> >> Reviewed-by: Carlos O'Donell <carlos@xxxxxxxxxx> > > Hi Carlos, > > Thanks! Does this apply to the entire patch set, or to this patch only? Only to this patch. I'll provide Reviewed-by's for individual patches in a series as I make it through review of a given series. Does that answer your question? > Have a lovely night! > Alex > >> >>> --- >>> man/man3/getcwd.3 | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/man/man3/getcwd.3 b/man/man3/getcwd.3 >>> index 919ffb08f..f3da4b5a9 100644 >>> --- a/man/man3/getcwd.3 >>> +++ b/man/man3/getcwd.3 >>> @@ -245,7 +245,7 @@ process (e.g., because the process set a new filesystem root using >>> without changing its current directory into the new root). >>> Such behavior can also be caused by an unprivileged user by changing >>> the current directory into another mount namespace. >>> -When dealing with pathname from untrusted sources, callers of the >>> +When dealing with pathnames from untrusted sources, callers of the >>> functions described in this page (until glibc 2.27) >>> or the raw >>> .BR getcwd () >> >> >> -- >> Cheers, >> Carlos. >> >> > -- Cheers, Carlos.
