linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] zonefs fixes for 6.5-rc6
Date: Sat, 12 Aug 2023 08:48:50 +0900	[thread overview]
Message-ID: <20230811234850.101951-1-dlemoal@kernel.org> (raw)

From: Damien Le Moal <damien.lemoal@opensource.wdc.com>

Linus,

The following changes since commit 52a93d39b17dc7eb98b6aa3edb93943248e03b2f:

  Linux 6.5-rc5 (2023-08-06 15:07:51 -0700)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/dlemoal/zonefs tags/zonefs-6.5-rc6

for you to fetch changes up to fe9da61ffccad80ae79fadad836971acf0d465bd:

  zonefs: fix synchronous direct writes to sequential files (2023-08-10 12:59:47 +0900)

----------------------------------------------------------------
zonefs fixes for 6.5-rc6

 - The switch to using iomap for executing direct synchronous write to
   sequential files using zone append BIO overlooked cases where the BIO
   built by iomap is too large and needs splitting, which is not allowed
   with zone append. Fix this by using regular write commands instead.
   The use of zone append commands will be reintroduces later with
   proper support from iomap.

----------------------------------------------------------------
Damien Le Moal (1):
      zonefs: fix synchronous direct writes to sequential files

 fs/zonefs/file.c   | 111 ++---------------------------------------------------
 fs/zonefs/super.c  |   9 +----
 fs/zonefs/zonefs.h |   2 -
 3 files changed, 4 insertions(+), 118 deletions(-)

             reply	other threads:[~2023-08-11 23:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 23:48 Damien Le Moal [this message]
2023-08-12  2:56 ` [GIT PULL] zonefs fixes for 6.5-rc6 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=20230811234850.101951-1-dlemoal@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=linux-fsdevel@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 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).