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: hch@lst.de, jstancek@redhat.com, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org
Subject: [GIT PULL] iomap: bug fixes for 6.6-rc7
Date: Fri, 20 Oct 2023 23:27:44 -0700	[thread overview]
Message-ID: <169786962623.1265253.5321166241579915281.stg-ugh@frogsfrogsfrogs> (raw)

Hi Linus,

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

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 684f7e6d28e8087502fc8efdb6c9fe82400479dd:

iomap: Spelling s/preceeding/preceding/g (2023-09-28 09:26:58 -0700)

are available in the Git repository at:

https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git iomap-6.6-fixes-5

for you to fetch changes up to 3ac974796e5d94509b85a403449132ea660127c2:

iomap: fix short copy in iomap_write_iter() (2023-10-19 09:41:36 -0700)

----------------------------------------------------------------
Bug fixes for 6.6-rc6:

* Fix a bug where a writev consisting of a bunch of sub-fsblock writes
where the last buffer address is invalid could lead to an infinite
loop.

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

----------------------------------------------------------------
Jan Stancek (1):
iomap: fix short copy in iomap_write_iter()

fs/iomap/buffered-io.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)

             reply	other threads:[~2023-10-21  6:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21  6:27 Darrick J. Wong [this message]
2023-10-21 16:46 ` [GIT PULL] iomap: bug fixes for 6.6-rc7 Linus Torvalds
2023-10-23 22:38   ` Darrick J. Wong
2023-10-24 11:47     ` Christian Brauner
2023-10-26  3:13       ` Darrick J. Wong
2023-10-26 11:54         ` Christian Brauner
2023-10-27  0:43           ` Darrick J. Wong
2023-10-26 18:10         ` Linus Torvalds
2023-10-26 20:20           ` Jeff Layton
2023-10-27 18:46           ` Christian Brauner
2023-10-27 23:30             ` Linus Torvalds
2023-10-28 16:56               ` Christian Brauner
2023-10-21 17:57 ` 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=169786962623.1265253.5321166241579915281.stg-ugh@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=jstancek@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@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 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.