All of lore.kernel.org
 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.18-rc5
Date: Wed, 27 Apr 2022 14:21:07 +0900	[thread overview]
Message-ID: <20220427052107.9812-1-damien.lemoal@opensource.wdc.com> (raw)

Linus,

The following changes since commit b2d229d4ddb17db541098b83524d901257e93845:

  Linux 5.18-rc3 (2022-04-17 13:57:31 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 1da18a296f5ba4f99429e62a7cf4fdbefa598902:

  zonefs: Fix management of open zones (2022-04-21 08:39:20 +0900)

----------------------------------------------------------------
zonefs fixes for 5.18-rc5

Two fixes for rc5:

* Fix inode initialization to make sure that the inode flags are all
  cleared.

* Use zone reset operation instead of close to make sure that the zone
  of an empty sequential file in never in an active state after closing
  the file.

----------------------------------------------------------------
Damien Le Moal (2):
      zonefs: Clear inode information flags on inode creation
      zonefs: Fix management of open zones

 fs/zonefs/super.c | 46 +++++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 41 insertions(+), 5 deletions(-)

             reply	other threads:[~2022-04-27  5:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  5:21 Damien Le Moal [this message]
2022-04-27 17:35 ` [GIT PULL] zonefs fixes for 5.18-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=20220427052107.9812-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 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.