From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
linux-fsdevel@vger.kernel.org
Subject: [git pull] bcachefs locking fix
Date: Fri, 12 Jan 2024 07:29:54 +0000 [thread overview]
Message-ID: <20240112072954.GC1674809@ZenIV> (raw)
Looks like Kent hadn't merged that into his branch for some reason;
IIRC, he'd been OK with the fix and had no objections to that stuff
sitting in -next, so...
Kent, if you *do* have objections, please make them now.
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-bcachefs-fix
for you to fetch changes up to bbe6a7c899e7f265c5a6d01a178336a405e98ed6:
bch2_ioctl_subvolume_destroy(): fix locking (2023-11-15 22:47:58 -0500)
----------------------------------------------------------------
fix buggered locking in bch2_ioctl_subvolume_destroy()
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (2):
new helper: user_path_locked_at()
bch2_ioctl_subvolume_destroy(): fix locking
fs/bcachefs/fs-ioctl.c | 31 +++++++++++++++++--------------
fs/namei.c | 16 +++++++++++++---
include/linux/namei.h | 1 +
3 files changed, 31 insertions(+), 17 deletions(-)
next reply other threads:[~2024-01-12 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 7:29 Al Viro [this message]
2024-01-12 15:22 ` [git pull] bcachefs locking fix Kent Overstreet
2024-01-12 19:25 ` Al Viro
2024-01-13 2:20 ` Kent Overstreet
2024-01-13 2:09 ` 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=20240112072954.GC1674809@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).