All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, torvalds@linux-foundation.org
Cc: dlemoal@kernel.org, hch@lst.de, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org, ritesh.list@gmail.com,
	willy@infradead.org,
	syzbot+4a08ffdf3667b36650a1@syzkaller.appspotmail.com
Subject: [GIT PULL] iomap: fix unshare data corruption bug
Date: Fri, 22 Sep 2023 17:39:01 -0700	[thread overview]
Message-ID: <169542943249.26581.2290117144266358331.stg-ugh@frogsfrogsfrogs> (raw)

Hi Linus,

Please pull this branch with changes for iomap for 6.6-rc3.

As usual, I did a test-merge with the main upstream branch as of a few
minutes ago, and didn't see any conflicts.  Please let me know if you
encounter any problems.

--D

The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:

Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)

are available in the Git repository at:

https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-6.6-fixes-2

for you to fetch changes up to a5f31a5028d1e88e97c3b6cdc3e3bf2da085e232:

iomap: convert iomap_unshare_iter to use large folios (2023-09-19 09:05:35 -0700)

----------------------------------------------------------------
Fixes for 6.6-rc3:

* Return EIO on bad inputs to iomap_to_bh instead of BUGging, to deal
less poorly with block device io racing with block device resizing.
* Fix a stale page data exposure bug introduced in 6.6-rc1 when
unsharing a file range that is not in the page cache.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>

----------------------------------------------------------------
Christoph Hellwig (1):
iomap: handle error conditions more gracefully in iomap_to_bh

Darrick J. Wong (2):
iomap: don't skip reading in !uptodate folios when unsharing a range
iomap: convert iomap_unshare_iter to use large folios

fs/buffer.c            | 25 ++++++++++++++-----------
fs/iomap/buffered-io.c | 30 ++++++++++++++++++------------
2 files changed, 32 insertions(+), 23 deletions(-)

             reply	other threads:[~2023-09-23  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23  0:39 Darrick J. Wong [this message]
2023-09-23 18:25 ` [GIT PULL] iomap: fix unshare data corruption bug 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=169542943249.26581.2290117144266358331.stg-ugh@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ritesh.list@gmail.com \
    --cc=syzbot+4a08ffdf3667b36650a1@syzkaller.appspotmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.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 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.