All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	Baokun Li <libaokun@linux.alibaba.com>
Subject: Re: [PATCH] block: fix bio_alloc_bioset() percpu cache fallback for non-reclaim contexts
Date: Wed, 8 Jul 2026 17:49:21 +0800	[thread overview]
Message-ID: <b8b95aeb-8443-404b-a320-e3bd3fed1598@linux.alibaba.com> (raw)
In-Reply-To: <20260708084547.GA3591@lst.de>



On 7/8/26 4:45 PM, Christoph Hellwig wrote:
> On Wed, Jul 08, 2026 at 09:14:13AM +0800, Joseph Qi wrote:
>> This causes virtio-pmem flush (async_pmem_flush) to fail with -ENOMEM
>> whenever the percpu bio cache happens to be empty (common right after
>> boot), making the device effectively unmountable:
> 
> Please fix that to not sure GFP_ATOMIC instead.  Flushes are used
> in file system writeabck and must not use potential failing allocations.
> 
> Even if you slightly increase the chance of it not failing, it still
> can and this code is simply broken.
> 

Looks sane. So commit b520c4eef83d exposed the bug but not introduced it.

>> Fix this by restructuring the allocation so that the percpu cache is
>> tried first when applicable, and the slab allocation is always attempted
>> as a common fallback path when the bio is still NULL.
> 
> I don;
> 
>>
>> Fixes: b520c4eef83d ("block: split bio_alloc_bioset more clearly into a fast and slowpath")
>> Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
>> ---
>>  block/bio.c | 5 +++++
>>  1 file changed, 5 insertions(+)
>>
>> diff --git a/block/bio.c b/block/bio.c
>> index f2a5f4d0a9672..9e7939861b94a 100644
>> --- a/block/bio.c
>> +++ b/block/bio.c
>> @@ -553,6 +553,11 @@ struct bio *bio_alloc_bioset(struct block_device *bdev, unsigned short nr_vecs,
>>  		 */
>>  		opf |= REQ_ALLOC_CACHE;
>>  		bio = bio_alloc_percpu_cache(bs);
>> +		if (!bio) {
>> +			p = kmem_cache_alloc(bs->bio_slab, gfp);
>> +			if (p)
>> +				bio = p + bs->front_pad;
>> +		}
> 
> But even if we wanted this, this code should not be duplicated by
> share the common version.

This is because I want to keep REQ_ALLOC_CACHE set.
Thanks for comments. I'll try to fix it in virtio-pmem driver.

Thanks,
Joseph

  reply	other threads:[~2026-07-08  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08  1:14 [PATCH] block: fix bio_alloc_bioset() percpu cache fallback for non-reclaim contexts Joseph Qi
2026-07-08  8:45 ` Christoph Hellwig
2026-07-08  9:49   ` Joseph Qi [this message]
2026-07-08 16:21     ` Christoph Hellwig
2026-07-09  1:21       ` Joseph Qi

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=b8b95aeb-8443-404b-a320-e3bd3fed1598@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=libaokun@linux.alibaba.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.