From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 4.14 v2 0/3] POLLFREE fix for 4.14
Date: Fri, 10 Dec 2021 16:19:23 -0800 [thread overview]
Message-ID: <20211211001926.100856-1-ebiggers@kernel.org> (raw)
This kernel version doesn't have aio poll, but the fix for POLLFREE with
exclusive waiters is still applicable to it. This series resolves
conflicts in all three patches, mostly due to POLLHUP having been
renamed to EPOLLHUP in more recent kernels.
v2: fix build break
Eric Biggers (3):
wait: add wake_up_pollfree()
binder: use wake_up_pollfree()
signalfd: use wake_up_pollfree()
drivers/android/binder.c | 21 +++++++++------------
fs/signalfd.c | 12 +-----------
include/linux/wait.h | 26 ++++++++++++++++++++++++++
kernel/sched/wait.c | 8 ++++++++
4 files changed, 44 insertions(+), 23 deletions(-)
--
2.34.1
next reply other threads:[~2021-12-11 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 0:19 Eric Biggers [this message]
2021-12-11 0:19 ` [PATCH 4.14 v2 1/3] wait: add wake_up_pollfree() Eric Biggers
2021-12-11 0:19 ` [PATCH 4.14 v2 2/3] binder: use wake_up_pollfree() Eric Biggers
2021-12-11 0:19 ` [PATCH 4.14 v2 3/3] signalfd: " Eric Biggers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211211001926.100856-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox