From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: jack@suse.cz, hch@lst.de
Subject: [ANNOUNCE] xfs-linux: vfs-for-next updated to 9b8523423b23
Date: Wed, 11 Nov 2020 09:01:31 -0800 [thread overview]
Message-ID: <20201111170131.GR9695@magnolia> (raw)
Hi folks,
The vfs-for-next branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update. This is a short branch fixing the fs freeze locking
races that we were discussing earlier this week. I haven't decided if I
really want to send the code cleanups for 5.10 (-fixes-2) but the first
tag (-fixes-1) solves some real corruption problems.
The new head of the vfs-for-next branch is commit:
9b8523423b23 vfs: move __sb_{start,end}_write* to fs.h
New Commits:
Darrick J. Wong (3):
[22843291efc9] vfs: remove lockdep bogosity in __sb_start_write
[8a3c84b649b0] vfs: separate __sb_start_write into blocking and non-blocking helpers
[9b8523423b23] vfs: move __sb_{start,end}_write* to fs.h
Code Diffstat:
fs/aio.c | 2 +-
fs/io_uring.c | 3 +--
fs/super.c | 49 -------------------------------------------------
include/linux/fs.h | 38 +++++++++++++++++++++++++++-----------
4 files changed, 29 insertions(+), 63 deletions(-)
reply other threads:[~2020-11-11 17:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201111170131.GR9695@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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 NNTP newsgroup(s).