mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-erofs@lists.ozlabs.org, Chao Yu <chao@kernel.org>,
	Yue Hu <huyue2@yulong.com>
Subject: [GIT PULL] erofs fix for 5.17-rc7
Date: Wed, 2 Mar 2022 22:41:14 +0800	[thread overview]
Message-ID: <Yh+CCr04nTTappWl@hsiangkao-PC> (raw)

Hi Linus,

Could you consider this pull request for 5.17-rc7?

It's a one-line patch to fix the new ztailpacking feature on > 4GiB
filesystems because z_idataoff can get trimmed improperly.

Even if ztailpacking is still a brand new EXPERIMENTAL feature, it'd
be better to fix the issue as soon as possible to avoid backporting
unnecessary..

The original patch has been in linux-next for a week and no merge
conflicts. Except that I added a new RVB tag from Chao today.

Thanks,
Gao Xiang

The following changes since commit cfb92440ee71adcc2105b0890bb01ac3cddb8507:

  Linux 5.17-rc5 (2022-02-20 13:07:20 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-5.17-rc7-fixes

for you to fetch changes up to 22ba5e99b96f1c0dbdfa4f4e1d9751b4c8348541:

  erofs: fix ztailpacking on > 4GiB filesystems (2022-03-02 21:58:45 +0800)

----------------------------------------------------------------
Change since last update:

 - Fix ztailpacking z_idataoff getting trimmed on > 4GiB filesystems.

----------------------------------------------------------------
Gao Xiang (1):
      erofs: fix ztailpacking on > 4GiB filesystems

 fs/erofs/internal.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2022-03-02 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 14:41 Gao Xiang [this message]
2022-03-02 20:36 ` 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=Yh+CCr04nTTappWl@hsiangkao-PC \
    --to=xiang@kernel.org \
    --cc=chao@kernel.org \
    --cc=huyue2@yulong.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®