linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Martin DEVERA <devik@eaxlabs.cz>,
	linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] erofs fix for 5.12-rc3
Date: Sat, 13 Mar 2021 20:40:44 +0800	[thread overview]
Message-ID: <20210313124044.GA488856@xiangao.remote.csb> (raw)

Hi Linus,

Could you consider this pull request for 5.11-rc3?
All details about this new regression are as below.

All commits have been tested and have been in -next for days.
This merges cleanly with master.

Thanks,
Gao Xiang

The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:

  Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-5.12-rc3

for you to fetch changes up to 9f377622a484de0818c49ee01e0ab4eedf6acd81:

  erofs: fix bio->bi_max_vecs behavior change (2021-03-08 10:43:32 +0800)

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

Fix an urgent regression introduced by commit baa2c7c97153 ("block:
set .bi_max_vecs as actual allocated vector number"), which could
cause unexpected hung since linux 5.12-rc1.

Resolve it by avoiding using bio->bi_max_vecs completely.

----------------------------------------------------------------
Gao Xiang (1):
      erofs: fix bio->bi_max_vecs behavior change

 fs/erofs/data.c | 28 +++++++++++-----------------
 1 file changed, 11 insertions(+), 17 deletions(-)


             reply	other threads:[~2021-03-13 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-13 12:40 Gao Xiang [this message]
2021-03-13 20:45 ` [GIT PULL] erofs fix for 5.12-rc3 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=20210313124044.GA488856@xiangao.remote.csb \
    --to=hsiangkao@redhat.com \
    --cc=devik@eaxlabs.cz \
    --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;
as well as URLs for NNTP newsgroup(s).