linux-kernel - Re: [PATCH] vfs: fix typo in link_path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <577BB818.4090009@osg.samsung.com>
Date:	Tue, 05 Jul 2016 14:37:28 +0100
From:	Luis de Bethencourt <luisbg@....samsung.com>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	osandov@...ndov.com
Subject: Re: [PATCH] vfs: fix typo in link_path_walk()

On 04/07/16 21:50, Al Viro wrote:
> On Mon, Jul 04, 2016 at 05:48:53PM +0100, Luis de Bethencourt wrote:
>> Comment documenting the path parsing in link_path_walk() has a typo, fixing
>> it.
> 
>> @@ -2064,7 +2064,7 @@ static int link_path_walk(const char *name, struct nameidata *nd)
>>  		if (!*name)
>>  			goto OK;
>>  		/*
>> -		 * If it wasn't NUL, we know it was '/'. Skip that
>> +		 * If it wasn't NULL, we know it was '/'. Skip that
> 
> "If it wasn't <this>, we know it was <that>" really implies that <this> and
> <that> are values possible for the same expression, doesn't it?  How could
> a pointer (NULL) and a character ('/') possibly be such?
> 
> Could you explain the meaning of thus "fixed" comment?  I'm not even asking
> to explain why it is correct that way, just what the hell is it supposed to
> mean?
> 
> NAK, in case it's not obvious from the above...
> 

Hi,

I was misinformed and thought NUL was only used as an abbreviation for the Null
character, and in a sentence the full name was meant to be used. As in,
null-terminated string. I didn't mean NULL pointer, since char *name is
dereferenced in the if check.

I see now that NULL can be more ambiguous than NUL or '\0'.
Sorry about that, I should had thought better before posting.

Apologies,
Luis