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 5.19-rc2
Date: Fri, 10 Jun 2022 19:51:13 +0900	[thread overview]
Message-ID: <20220610105113.788534-1-damien.lemoal@opensource.wdc.com> (raw)

Linus,

The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:

  Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)

are available in the Git repository at:

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

for you to fetch changes up to c1c1204c0d0c1dccc1310b9277fb2bd8b663d8fe:

  zonefs: fix zonefs_iomap_begin() for reads (2022-06-08 19:13:55 +0900)

----------------------------------------------------------------
zonefs fixes for 5.19-rc2

* Fix handling of the explicit-open mount option, and in particular the
  conditions under which this option can be ignored.

* Fix a problem with zonefs iomap_begin method, causing a hang in
  iomap_readahead() when a readahead request reaches the end of a file.

----------------------------------------------------------------
Damien Le Moal (3):
      zonefs: fix handling of explicit_open option on mount
      zonefs: Do not ignore explicit_open with active zone limit
      zonefs: fix zonefs_iomap_begin() for reads

 fs/zonefs/super.c | 111 ++++++++++++++++++++++++++++++++++++------------------
 1 file changed, 74 insertions(+), 37 deletions(-)

             reply	other threads:[~2022-06-10 10:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 10:51 Damien Le Moal [this message]
2022-06-10 18:25 ` [GIT PULL] zonefs fixes for 5.19-rc2 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=20220610105113.788534-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).