[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20230406-kernig-parabel-d12963a4e7fa@brauner>
Date: Thu, 6 Apr 2023 11:08:49 +0200
From: Christian Brauner <brauner@...nel.org>
To: wenyang.linux@...mail.com
Cc: Christian Brauner <brauner@...nel.org>,
Eric Biggers <ebiggers@...gle.com>,
Christoph Hellwig <hch@....de>, Dylan Yudaken <dylany@...com>,
David Woodhouse <dwmw@...zon.co.uk>, Fu Wei <wefu@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Michal Nazarewicz <m.nazarewicz@...sung.com>,
Matthew Wilcox <willy@...radead.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
Jens Axboe <axboe@...nel.dk>
Subject: Re: [RESEND PATCH v2] eventfd: use wait_event_interruptible_locked_irq() helper
On Thu, 06 Apr 2023 03:20:02 +0800, wenyang.linux@...mail.com wrote:
> wait_event_interruptible_locked_irq was introduced by commit 22c43c81a51e
> ("wait_event_interruptible_locked() interface"), but older code such as
> eventfd_{write,read} still uses the open code implementation.
> Inspired by commit 8120a8aadb20
> ("fs/timerfd.c: make use of wait_event_interruptible_locked_irq()"), this
> patch replaces the open code implementation with a single macro call.
>
> [...]
I ran LTP with ./runltp -f syscalls -s eventfd passes and aligns with what was
done for timerfd.
Applied, thanks!
tree: git://git.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping.git
branch: fs.misc
[1/1] eventfd: use wait_event_interruptible_locked_irq() helper
commit: 113348a44b8622b497fb884f41c8659481ad0b04
Powered by blists - more mailing lists