public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
	linux-block <linux-block@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
	Changheun Lee <nanich.lee@samsung.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Bruno Goncalves <bgoncalv@redhat.com>
Subject: Re: [PATCH v2] block: Improve limiting the bio size
Date: Mon, 26 Apr 2021 06:54:37 -0600	[thread overview]
Message-ID: <0f078c05-b212-3877-fa64-77fd79cc50ce@kernel.dk> (raw)
In-Reply-To: <CAHj4cs9E+9n9M6W59LuTWQbbhTzMGgi8KBPaN+cAYC3ypC3dCg@mail.gmail.com>

On 4/26/21 12:32 AM, Yi Zhang wrote:
> Hi Jens/Bart
> CKI reproduced the boot panic issue again with the latest
> linux-block/for-next[1] today, then I checked the patch 'bio: limit
> bio max size'[2] found Bart's fix patch does not fold in that commit,
> could you help recheck it, thanks.

Hmm, maybe I botched it. But a bit too much churn around this patch,
Changheun maybe you can resend a fully tested version?

-- 
Jens Axboe


  parent reply	other threads:[~2021-04-26 12:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25  4:30 [PATCH v2] block: Improve limiting the bio size Bart Van Assche
2021-04-25  7:36 ` Yi Zhang
2021-04-25 16:19 ` Jens Axboe
2021-04-26  6:32   ` Yi Zhang
2021-04-26  8:34     ` Changheun Lee
2021-04-26 16:17       ` Bart Van Assche
2021-04-27  0:28         ` Changheun Lee
2021-04-27  2:46           ` Bart Van Assche
2021-04-27  4:12             ` Changheun Lee
2021-04-27 14:59               ` Bart Van Assche
2021-04-28  7:21                 ` Changheun Lee
2021-04-28 15:52                   ` Bart Van Assche
2021-04-29  6:39                     ` Changheun Lee
2021-05-03  9:28                       ` Changheun Lee
2021-05-03 16:35                         ` Bart Van Assche
2021-04-26 12:54     ` Jens Axboe [this message]
2021-04-26 23:43       ` Changheun Lee

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=0f078c05-b212-3877-fa64-77fd79cc50ce@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=bgoncalv@redhat.com \
    --cc=bvanassche@acm.org \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=nanich.lee@samsung.com \
    --cc=yi.zhang@redhat.com \
    /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