[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8e7c0d56-64f3-d0b6-c1cf-9f285c59f169@redhat.com>
Date: Sun, 29 Nov 2020 09:47:18 -0800
From: Tom Rix <trix@...hat.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: jlayton@...nel.org, bfields@...ldses.org, viro@...iv.linux.org.uk,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] locks: remove trailing semicolon in macro definition
On 11/27/20 11:53 AM, Matthew Wilcox wrote:
> On Fri, Nov 27, 2020 at 11:07:07AM -0800, trix@...hat.com wrote:
>> +++ b/fs/fcntl.c
>> @@ -526,7 +526,7 @@ SYSCALL_DEFINE3(fcntl64, unsigned int, fd, unsigned int, cmd,
>> (dst)->l_whence = (src)->l_whence; \
>> (dst)->l_start = (src)->l_start; \
>> (dst)->l_len = (src)->l_len; \
>> - (dst)->l_pid = (src)->l_pid;
>> + (dst)->l_pid = (src)->l_pid
> This should be wrapped in a do { } while (0).
>
> Look, this warning is clearly great at finding smelly code, but the
> fixes being generated to shut up the warning are low quality.
>
Multiline macros not following the do {} while (0) pattern are likely a larger problem.
I'll take a look.
Thanks,
Tom
Powered by blists - more mailing lists