From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
Doug Gilbert <dgilbert@interlog.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: fix /dev/sg allocation failures register
Date: Mon, 20 Apr 2026 22:17:23 -0400 [thread overview]
Message-ID: <yq1y0ihoy69.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260415060813.807659-1-hch@lst.de> (Christoph Hellwig's message of "Wed, 15 Apr 2026 08:08:05 +0200")
Christoph,
> This series has two independent patches to fix this from different
> angles. The first one changes the completely pointless GFP_ATOMIC to
> use GFP_ATOMIC in sg. The other drops the reduction of the gfp mask in
> the bio allocator, so that atomic allocations of bios work as
> expected, even if they are a pretty bad idea as the bio submission
> actually needs a user context anyway. The only other uses of this
> seems to be the ocfs2 cluster managed.
Applied #1 to 7.1/scsi-staging, thanks!
#2 needs to go through block.
--
Martin K. Petersen
prev parent reply other threads:[~2026-04-21 2:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 6:08 fix /dev/sg allocation failures register Christoph Hellwig
2026-04-15 6:08 ` [PATCH 1/2] sg: don't use GFP_ATOMIC in sg_start_req Christoph Hellwig
2026-04-15 8:02 ` John Garry
2026-04-16 6:25 ` Hannes Reinecke
2026-04-16 15:05 ` Bart Van Assche
2026-04-21 17:42 ` (subset) " Jens Axboe
2026-04-15 6:08 ` [PATCH 2/2] block: only restrict bio allocation gfp mask asked to block Christoph Hellwig
2026-04-16 6:26 ` Hannes Reinecke
2026-04-16 15:07 ` Bart Van Assche
2026-04-21 2:17 ` Martin K. Petersen [this message]
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=yq1y0ihoy69.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=dgilbert@interlog.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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