From: Baoquan He <bhe@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2] sr: don't use GFP_DMA
Date: Wed, 22 Dec 2021 17:37:07 +0800 [thread overview]
Message-ID: <20211222093707.GA23698@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20211222090842.920724-1-hch@lst.de>
Hi Christoph,
On 12/22/21 at 10:08am, Christoph Hellwig wrote:
> The allocated buffers are used as a command payload, for which the block
> layer and/or DMA API do the proper bounce buffering if needed.
>
> Reported-by: Baoquan He <bhe@redhat.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>
> Changes since v1:
> - also cover the two callsites in sr_vendor.c
>
> Diffstat:
> drivers/scsi/sr.c | 2 +-
> drivers/scsi/sr_vendor.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/scsi/sr.c b/drivers/scsi/sr.c
> index 14c122839c409..f925b1f1f9ada 100644
> --- a/drivers/scsi/sr.c
> +++ b/drivers/scsi/sr.c
> @@ -855,7 +855,7 @@ static void get_capabilities(struct scsi_cd *cd)
>
>
> /* allocate transfer buffer */
> - buffer = kmalloc(512, GFP_KERNEL | GFP_DMA);
> + buffer = kmalloc(512, GFP_KERNEL);
Thanks a lot for doing this. When I browsed the code path, I come to
blk_rq_map_kern() but I am not sure if blk_queue_may_bounce() is true in
the sr_probe() case, then it may enter into bio_map_kern().
Next I will post my original patchset to mute the allocation failure if
it's requesting page from DMA zone and DMA zone has no managed page. And
meanwhile, I will try to collect those places of kmalloc(GFP_DMA) into a
RFC mail, see if we can change them one by one. Anyone can pick one
place to fix if interested or knowing it well. Finally, we can remove the
need of dma-kmalloc() as people suggested. Any comment?
For this patch, it's an awesome start, thx.
Reviewed-by: Baoquan He <bhe@redhat.com>
> if (!buffer) {
> sr_printk(KERN_ERR, cd, "out of memory.\n");
> return;
> diff --git a/drivers/scsi/sr_vendor.c b/drivers/scsi/sr_vendor.c
> index 1f988a1b9166f..a61635326ae0a 100644
> --- a/drivers/scsi/sr_vendor.c
> +++ b/drivers/scsi/sr_vendor.c
> @@ -131,7 +131,7 @@ int sr_set_blocklength(Scsi_CD *cd, int blocklength)
> if (cd->vendor == VENDOR_TOSHIBA)
> density = (blocklength > 2048) ? 0x81 : 0x83;
>
> - buffer = kmalloc(512, GFP_KERNEL | GFP_DMA);
> + buffer = kmalloc(512, GFP_KERNEL);
> if (!buffer)
> return -ENOMEM;
>
> @@ -179,7 +179,7 @@ int sr_cd_check(struct cdrom_device_info *cdi)
> if (cd->cdi.mask & CDC_MULTI_SESSION)
> return 0;
>
> - buffer = kmalloc(512, GFP_KERNEL | GFP_DMA);
> + buffer = kmalloc(512, GFP_KERNEL);
> if (!buffer)
> return -ENOMEM;
>
> --
> 2.30.2
>
next prev parent reply other threads:[~2021-12-22 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 9:08 [PATCH v2] sr: don't use GFP_DMA Christoph Hellwig
2021-12-22 9:37 ` Baoquan He [this message]
2021-12-22 9:42 ` Christoph Hellwig
2021-12-22 10:40 ` Baoquan He
2021-12-23 9:01 ` Christoph Hellwig
2021-12-23 9:16 ` Baoquan He
2021-12-23 4:45 ` Martin K. Petersen
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=20211222093707.GA23698@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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