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: <0FE857A7-F8B7-453C-BB81-AA012D45E578@gmail.com>
Date:   Mon, 7 Mar 2022 11:47:30 +0100
From:   Jakob Koschel <jakobkoschel@...il.com>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Greg Kroah-Hartman <greg@...ah.com>,
        Mike Rapoport <rppt@...nel.org>,
        Brian Johannesmeyer <bjohannesmeyer@...il.com>,
        Cristiano Giuffrida <c.giuffrida@...nl>,
        "Bos, H.J." <h.j.bos@...nl>
Subject: Re: [PATCH] list: always set pos in list_prepare_entry()



> On 7. Mar 2022, at 10:49, Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
> 
> On Sun, Mar 06, 2022 at 05:26:35PM +0100, Jakob Koschel wrote:
>> In order to assign the result from list_prepare_entry() to another
>> variable, it should also be set when pos != NULL.
>> 
>> This will be useful once the list iterator is no longer used after
>> the loop.
> 
> ...
> 
>> #define list_prepare_entry(pos, head, member) \
>> -	((pos) ? : list_entry(head, typeof(*pos), member))
>> +	((pos) ? pos : list_entry(head, typeof(*pos), member))
> 
> I'm not sure why then we have () surrounding first pos.
> 
> Am I right that the original is an equivalent to
> 
> 	((pos) ? (pos) : list_entry(head, typeof(*pos), member))
> 
> ?

Yes you are right.

I've just tested this again and seems like my local setup was skewed.

My assumption (from some coccinelle output) was that leaving the TRUE case
empty will not do any assignment at all but that's obviously wrong and I
can't reproduce it.

Basically feel free to ignore this PATCH since it just seems to be a NO-OP.

> 
> Then what the difference is made by not using parentheses?
> 
> -- 
> With Best Regards,
> Andy Shevchenko
> 
> 

Jakob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ