[<prev] [next>] [day] [month] [year] [list]
Message-ID: <ZKsTHWjJsvLw6kJo@casper.infradead.org>
Date: Sun, 9 Jul 2023 21:05:49 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Markus Elfring <Markus.Elfring@....de>
Cc: Wen Yang <wenyang.linux@...mail.com>,
linux-fsdevel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Jens Axboe <axboe@...nel.dk>,
LKML <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
David Woodhouse <dwmw@...zon.co.uk>,
Dylan Yudaken <dylany@...com>
Subject: Re: [PATCH] eventfd: avoid overflow to ULLONG_MAX when ctx->count is
0
On Sun, Jul 09, 2023 at 09:13:28PM +0200, Markus Elfring wrote:
> > For eventfd with flag EFD_SEMAPHORE, when its ctx->count is 0, calling
> > eventfd_ctx_do_read will cause ctx->count to overflow to ULLONG_MAX.
>
> Please choose an imperative change suggestion.
Markus, stop this nitpicking. It puts off contributors. The changelog
is perfectly clear.
Powered by blists - more mailing lists