From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: dgilbert@interlog.com
Cc: error27@gmail.com, harshit.m.mogalapalli@gmail.com,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: scsi_debug: Fix a warning in resp_write_scat()
Date: Sat, 12 Nov 2022 12:43:40 +0530 [thread overview]
Message-ID: <fa578a51-5bae-21be-df5b-a72f5f79c662@oracle.com> (raw)
In-Reply-To: <ffef9612-00da-43d2-caad-4f71a7ef7e44@interlog.com>
Hi Doug,
On 11/11/22 10:53 pm, Douglas Gilbert wrote:
> On 2022-11-11 05:05, Harshit Mogalapalli wrote:
>> As 'lbdof_blen' is coming from user, if the size in kzalloc()
>> is >= MAX_ORDER then we hit a warning.
>>
>> Call trace:
>>
>> sg_ioctl
>> sg_ioctl_common
>> scsi_ioctl
>> sg_scsi_ioctl
>> blk_execute_rq
>> blk_mq_sched_insert_request
>> blk_mq_run_hw_queue
>> __blk_mq_delay_run_hw_queue
>> __blk_mq_run_hw_queue
>> blk_mq_sched_dispatch_requests
>> __blk_mq_sched_dispatch_requests
>> blk_mq_dispatch_rq_list
>> scsi_queue_rq
>> scsi_dispatch_cmd
>> scsi_debug_queuecommand
>> schedule_resp
>> resp_write_scat
>>
>> If you try to allocate a memory larger than(>=) MAX_ORDER, then kmalloc()
>> will definitely fail. It creates a stack trace and messes up dmesg.
>> The user controls the size here so if they specify a too large size it
>> will fail.
>>
>> Add __GFP_NOWARN in order to avoid too large allocation warning.
>> This is detected by static analysis using smatch.
>>
>> Fixes: 481b5e5c7949 ("scsi: scsi_debug: add resp_write_scat function")
>> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
>
> Acked-by: Douglas Gilbert <dgilbert@interlog.com>
>
Thank you very much for checking the patch.
We have two more similar cases in the scsi_debug.c file in resp_verify()
and resp_report_zones() functions. These are also detected using static
analysis with smatch.
I have sent out patches for those.
Thanks,
Harshit
> Thanks.
>
>> ---
>> drivers/scsi/scsi_debug.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
>> index 697fc57bc711..273224d29ce9 100644
>> --- a/drivers/scsi/scsi_debug.c
>> +++ b/drivers/scsi/scsi_debug.c
>> @@ -3778,7 +3778,7 @@ static int resp_write_scat(struct scsi_cmnd *scp,
>> mk_sense_buffer(scp, ILLEGAL_REQUEST, INVALID_FIELD_IN_CDB, 0);
>> return illegal_condition_result;
>> }
>> - lrdp = kzalloc(lbdof_blen, GFP_ATOMIC);
>> + lrdp = kzalloc(lbdof_blen, GFP_ATOMIC | __GFP_NOWARN);
>> if (lrdp == NULL)
>> return SCSI_MLQUEUE_HOST_BUSY;
>> if (sdebug_verbose)
>
next prev parent reply other threads:[~2022-11-12 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 10:05 Harshit Mogalapalli
2022-11-11 17:23 ` Douglas Gilbert
2022-11-12 7:13 ` Harshit Mogalapalli [this message]
2022-11-17 18:12 ` Martin K. Petersen
2022-11-26 3:27 ` 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=fa578a51-5bae-21be-df5b-a72f5f79c662@oracle.com \
--to=harshit.m.mogalapalli@oracle.com \
--cc=dgilbert@interlog.com \
--cc=error27@gmail.com \
--cc=harshit.m.mogalapalli@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®