From: Kent Overstreet <kent.overstreet@linux.dev>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] bcachefs fixes for 6.8-rc4
Date: Mon, 5 Feb 2024 19:15:32 -0500 [thread overview]
Message-ID: <v6czqjwdsso2hy6be7qeu4mqxsx4oydq6shavws4k7sexshcrp@np4inrse4e4p> (raw)
The following changes since commit d2fda304bb739b97c1a3e46e39700eb49f07a62c:
bcachefs: __lookup_dirent() works in snapshot, not subvol (2024-01-25 20:02:11 -0500)
are available in the Git repository at:
https://evilpiepirate.org/git/bcachefs.git tags/bcachefs-2024-02-05
for you to fetch changes up to 7b508b323b2ec45be59769bd4e4aeba729c52cf6:
bcachefs: time_stats: Check for last_event == 0 when updating freq stats (2024-02-05 01:16:31 -0500)
----------------------------------------------------------------
bcachefs fixes for v6.8-rc4
Two serious ones here that we'll want to backport to stable: a fix for a
race in the thread_with_file code, and another locking fixup in the
subvolume deletion path.
----------------------------------------------------------------
Guoyu Ou (1):
bcachefs: unlock parent dir if entry is not found in subvolume deletion
Helge Deller (1):
bcachefs: Fix build on parisc by avoiding __multi3()
Kent Overstreet (1):
bcachefs: time_stats: Check for last_event == 0 when updating freq stats
Mathias Krause (1):
bcachefs: install fd later to avoid race with close
fs/bcachefs/fs-ioctl.c | 4 ++--
fs/bcachefs/mean_and_variance.h | 2 +-
fs/bcachefs/thread_with_file.c | 2 +-
fs/bcachefs/util.c | 5 +++--
4 files changed, 7 insertions(+), 6 deletions(-)
next reply other threads:[~2024-02-06 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 0:15 Kent Overstreet [this message]
2024-02-06 7:47 ` [GIT PULL] bcachefs fixes for 6.8-rc4 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=v6czqjwdsso2hy6be7qeu4mqxsx4oydq6shavws4k7sexshcrp@np4inrse4e4p \
--to=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@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 read-only IMAP folder(s) and NNTP newsgroup(s).