From: Kent Overstreet <kent.overstreet@linux.dev>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: [GIT PULL] bcachefs stable updates for v6.7
Date: Thu, 8 Feb 2024 20:14:39 -0500 [thread overview]
Message-ID: <6yl6zvu2pa3mz7irsaax5ivp6kh3dae5kaslvst7yafmg6672g@mskleu2vjfp2> (raw)
Hi Greg, few stable updates for you -
Cheers,
Kent
The following changes since commit 0dd3ee31125508cd67f7e7172247f05b7fd1753a:
Linux 6.7 (2024-01-07 12:18:38 -0800)
are available in the Git repository at:
https://evilpiepirate.org/git/bcachefs.git tags/bcachefs-for-v6.7-stable-20240208
for you to fetch changes up to f1582f4774ac7c30c5460a8c7a6e5a82b9ce5a6a:
bcachefs: time_stats: Check for last_event == 0 when updating freq stats (2024-02-08 15:33:11 -0500)
----------------------------------------------------------------
bcachefs updates for v6.7 stable:
locking fixes in subvolume create, destroy paths - Al, Su Yue, Guoyu Ou
fix race in thread_with_file - Mathias Krause
small rebalance fixes - Daniel, myself
workaround for building with old clang (can't take a pointer to memcmp)
build fix on parisc
minor time_stats fix
----------------------------------------------------------------
Al Viro (2):
new helper: user_path_locked_at()
bch2_ioctl_subvolume_destroy(): fix locking
Christoph Hellwig (1):
bcachefs: fix incorrect usage of REQ_OP_FLUSH
Daniel Hill (1):
bcachefs: rebalance should wakeup on shutdown if disabled
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 (4):
bcachefs: Don't pass memcmp() as a pointer
bcachefs: Add missing bch2_moving_ctxt_flush_all()
bcachefs: bch2_kthread_io_clock_wait() no longer sleeps until full amount
bcachefs: time_stats: Check for last_event == 0 when updating freq stats
Mathias Krause (1):
bcachefs: install fd later to avoid race with close
Su Yue (2):
bcachefs: kvfree bch_fs::snapshots in bch2_fs_snapshots_exit
bcachefs: grab s_umount only if snapshotting
fs/bcachefs/chardev.c | 3 +--
fs/bcachefs/clock.c | 4 ++--
fs/bcachefs/fs-io.c | 2 +-
fs/bcachefs/fs-ioctl.c | 42 +++++++++++++++++++++--------------------
fs/bcachefs/journal_io.c | 3 ++-
fs/bcachefs/mean_and_variance.h | 2 +-
fs/bcachefs/move.c | 2 +-
fs/bcachefs/move.h | 1 +
fs/bcachefs/rebalance.c | 13 +++++++++++--
fs/bcachefs/replicas.c | 10 ++++++++--
fs/bcachefs/snapshot.c | 2 +-
fs/bcachefs/util.c | 5 +++--
fs/namei.c | 16 +++++++++++++---
include/linux/namei.h | 1 +
14 files changed, 68 insertions(+), 38 deletions(-)
next reply other threads:[~2024-02-09 1:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 1:14 Kent Overstreet [this message]
2024-02-13 14:38 ` [GIT PULL] bcachefs stable updates for v6.7 Greg Kroah-Hartman
2024-02-13 14:44 ` Greg Kroah-Hartman
2024-02-14 2:28 ` Kent Overstreet
2024-02-14 6:51 ` Greg Kroah-Hartman
2024-02-20 14:34 ` Greg Kroah-Hartman
2024-02-20 17:25 ` Kent Overstreet
2024-02-20 18:02 ` Greg Kroah-Hartman
2024-02-14 2:16 ` Kent Overstreet
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=6yl6zvu2pa3mz7irsaax5ivp6kh3dae5kaslvst7yafmg6672g@mskleu2vjfp2 \
--to=kent.overstreet@linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-bcachefs@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).