All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	linux-xfs@vger.kernel.org, david@fromorbit.com,
	fdmanana@kernel.org, linux-fsdevel@vger.kernel.org,
	Jan Kara <jack@suse.cz>, Theodore Ts'o <tytso@mit.edu>
Subject: [GIT PULL] vfs: fs freeze fix for 5.10-rc4 (part 2)
Date: Fri, 13 Nov 2020 16:01:29 -0800	[thread overview]
Message-ID: <20201114000129.GY9695@magnolia> (raw)

Hi Linus,

The bug fix in the vfs pull request that I just sent you makes
__sb_start_write simple enough that it becomes possible to refactor the
function into smaller, simpler static inline helpers in linux/fs.h.  The
cleanup is straightforward, but as we're well into the stabilization
phase for 5.10, I'm perfectly happy to defer this to 5.11.

These changes also merge cleanly with upstream as of a few minutes ago,
so please let me know if anything strange happens.

--D

The following changes since commit 22843291efc986ce7722610073fcf85a39b4cb13:

  vfs: remove lockdep bogosity in __sb_start_write (2020-11-10 16:49:29 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/vfs-5.10-fixes-2

for you to fetch changes up to 9b8523423b23ee3dfd88e32f5b7207be56a4e782:

  vfs: move __sb_{start,end}_write* to fs.h (2020-11-10 16:53:11 -0800)

----------------------------------------------------------------
More VFS fixes for 5.10-rc4:
- Minor cleanups of the sb_start_* fs freeze helpers.

----------------------------------------------------------------
Darrick J. Wong (2):
      vfs: separate __sb_start_write into blocking and non-blocking helpers
      vfs: move __sb_{start,end}_write* to fs.h

 fs/aio.c           |  2 +-
 fs/io_uring.c      |  3 +--
 fs/super.c         | 24 ------------------------
 include/linux/fs.h | 38 +++++++++++++++++++++++++++-----------
 4 files changed, 29 insertions(+), 38 deletions(-)

             reply	other threads:[~2020-11-14  0:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14  0:01 Darrick J. Wong [this message]
2020-11-14  0:15 ` [GIT PULL] vfs: fs freeze fix for 5.10-rc4 (part 2) 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=20201114000129.GY9695@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=fdmanana@kernel.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.