From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Douglas Gilbert <dgilbert@interlog.com>,
error27@gmail.com, harshit.m.mogalapalli@gmail.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: [PATCH] scsi: scsi_debug: Fix a warning in resp_write_scat()
Date: Sat, 26 Nov 2022 03:27:36 +0000 [thread overview]
Message-ID: <166943312543.1684293.3175127415315924733.b4-ty@oracle.com> (raw)
In-Reply-To: <20221111100526.1790533-1-harshit.m.mogalapalli@oracle.com>
On Fri, 11 Nov 2022 02:05:25 -0800, 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
>
> [...]
Applied to 6.2/scsi-queue, thanks!
[1/1] scsi: scsi_debug: Fix a warning in resp_write_scat()
https://git.kernel.org/mkp/scsi/c/216e179724c1
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-11-26 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 10:05 [PATCH] scsi: scsi_debug: Fix a warning in resp_write_scat() Harshit Mogalapalli
2022-11-11 17:23 ` Douglas Gilbert
2022-11-12 7:13 ` Harshit Mogalapalli
2022-11-17 18:12 ` Martin K. Petersen
2022-11-26 3:27 ` 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=166943312543.1684293.3175127415315924733.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=dgilbert@interlog.com \
--cc=error27@gmail.com \
--cc=harshit.m.mogalapalli@gmail.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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.