From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"boqun.feng" <boqun.feng@gmail.com>,
Luo Meng <luomeng12@huawei.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: [GIT PULL] file locking fixes for 5.11
Date: Mon, 14 Dec 2020 08:22:46 -0500 [thread overview]
Message-ID: <f325fd49b5e185cf77a906db48ed590a46c75ef6.camel@kernel.org> (raw)
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git locks-v5.11
for you to fetch changes up to 8d1ddb5e79374fb277985a6b3faa2ed8631c5b4c:
fcntl: Fix potential deadlock in send_sig{io, urg}() (2020-11-05 07:44:15 -0500)
----------------------------------------------------------------
A fix for some undefined integer overflow behavior, a typo in a comment
header, and a fix for a potential deadlock involving internal senders of
SIGIO/SIGURG.
----------------------------------------------------------------
Boqun Feng (1):
fcntl: Fix potential deadlock in send_sig{io, urg}()
Luo Meng (1):
locks: Fix UBSAN undefined behaviour in flock64_to_posix_lock
Mauro Carvalho Chehab (1):
locks: fix a typo at a kernel-doc markup
fs/fcntl.c | 10 ++++++----
fs/locks.c | 4 ++--
2 files changed, 8 insertions(+), 6 deletions(-)
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2020-12-14 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 13:22 Jeff Layton [this message]
2020-12-16 3:44 ` pr-tracker-bot
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=f325fd49b5e185cf77a906db48ed590a46c75ef6.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luomeng12@huawei.com \
--cc=mchehab@infradead.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®