All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Yue Hu <huyue2@coolpad.com>,
	linux-erofs@lists.ozlabs.org
Subject: [GIT PULL] erofs fix for 6.8-rc6
Date: Sun, 25 Feb 2024 21:46:42 +0800	[thread overview]
Message-ID: <ZdtEwtN2BsCYnCeY@debian> (raw)

Hi Linus,

Could you consider this fix for 6.8-rc6?

The detailed description is as below and I think it'd be
much better to be landed now than later.

It has been in -next and no potential merge conflict is observed.

Thanks,
Gao Xiang

The following changes since commit 841c35169323cd833294798e58b9bf63fa4fa1de:

  Linux 6.8-rc4 (2024-02-11 12:18:13 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.8-rc6-fixes

for you to fetch changes up to 56ee7db31187dc36d501622cb5f1415e88e01c2a:

  erofs: fix refcount on the metabuf used for inode lookup (2024-02-22 15:54:21 +0800)

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

 - Fix page refcount leak when looking up specific inodes
   introduced by metabuf reworking.

----------------------------------------------------------------
Sandeep Dhavale (1):
      erofs: fix refcount on the metabuf used for inode lookup

 fs/erofs/namei.c | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
	Sandeep Dhavale <dhavale@google.com>, Chao Yu <chao@kernel.org>,
	Jingbo Xu <jefflexu@linux.alibaba.com>,
	Yue Hu <huyue2@coolpad.com>
Subject: [GIT PULL] erofs fix for 6.8-rc6
Date: Sun, 25 Feb 2024 21:46:42 +0800	[thread overview]
Message-ID: <ZdtEwtN2BsCYnCeY@debian> (raw)

Hi Linus,

Could you consider this fix for 6.8-rc6?

The detailed description is as below and I think it'd be
much better to be landed now than later.

It has been in -next and no potential merge conflict is observed.

Thanks,
Gao Xiang

The following changes since commit 841c35169323cd833294798e58b9bf63fa4fa1de:

  Linux 6.8-rc4 (2024-02-11 12:18:13 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.8-rc6-fixes

for you to fetch changes up to 56ee7db31187dc36d501622cb5f1415e88e01c2a:

  erofs: fix refcount on the metabuf used for inode lookup (2024-02-22 15:54:21 +0800)

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

 - Fix page refcount leak when looking up specific inodes
   introduced by metabuf reworking.

----------------------------------------------------------------
Sandeep Dhavale (1):
      erofs: fix refcount on the metabuf used for inode lookup

 fs/erofs/namei.c | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

             reply	other threads:[~2024-02-25 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 13:46 Gao Xiang [this message]
2024-02-25 13:46 ` [GIT PULL] erofs fix for 6.8-rc6 Gao Xiang
2024-02-25 17:57 ` pr-tracker-bot
2024-02-25 17:57   ` 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=ZdtEwtN2BsCYnCeY@debian \
    --to=xiang@kernel.org \
    --cc=huyue2@coolpad.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linuxfoundation.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.