linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] zonefs fixes for 6.3-rc5
Date: Thu, 30 Mar 2023 21:22:00 +0900	[thread overview]
Message-ID: <20230330122200.2663128-1-damien.lemoal@opensource.wdc.com> (raw)

Linus,

The following changes since commit 197b6b60ae7bc51dd0814953c562833143b292aa:

  Linux 6.3-rc4 (2023-03-26 14:40:20 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 77af13ba3c7f91d91c377c7e2d122849bbc17128:

  zonefs: Do not propagate iomap_dio_rw() ENOTBLK error to user space (2023-03-30 20:56:02 +0900)

----------------------------------------------------------------
zonefs fixes for 6.3-rc5

 * Make sure to always invalidate the last page of an inode straddling
   inode->i_size to avoid data inconsistencies with appended data when
   the device zone write granularity does not match the page size.

 * Do not propagate iomap -ENOBLK error to userspace and use -EBUSY
   instead.

----------------------------------------------------------------
Damien Le Moal (2):
      zonefs: Always invalidate last cached page on append write
      zonefs: Do not propagate iomap_dio_rw() ENOTBLK error to user space

 fs/zonefs/file.c | 28 ++++++++++++++++++++++++++--
 1 file changed, 26 insertions(+), 2 deletions(-)

             reply	other threads:[~2023-03-30 12:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 12:22 Damien Le Moal [this message]
2023-03-30 16:45 ` [GIT PULL] zonefs fixes for 6.3-rc5 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=20230330122200.2663128-1-damien.lemoal@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --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).