From: Oleksandr Natalenko <oleksandr@redhat.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Saurav Kashyap <skashyap@marvell.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
David Laight <David.Laight@aculab.com>,
GR-QLogic-Storage-Upstream@marvell.com,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Jozef Bacik <jobacik@redhat.com>,
Laurence Oberman <loberman@redhat.com>,
Rob Evers <revers@redhat.com>
Subject: Re: [PATCH v2 0/3] scsi: qedf: sanitise uaccess
Date: Tue, 01 Aug 2023 08:21:05 +0200 [thread overview]
Message-ID: <2290359.ElGaqSPkdT@redhat.com> (raw)
In-Reply-To: <yq1edknrkfk.fsf@ca-mkp.ca.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
On pondělí 31. července 2023 20:43:34 CEST Martin K. Petersen wrote:
>
> Oleksandr,
>
> > qedf driver, debugfs part of it specifically, touches __user pointers
> > directly for printing out info to userspace via sprintf(), which may
> > cause crash like this:
>
> Applied to 6.6/scsi-staging, thanks!
Thank you all.
--
Oleksandr Natalenko (post-factum)
Principal Software Maintenance Engineer
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-01 6:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 8:40 [PATCH v2 0/3] scsi: qedf: sanitise uaccess Oleksandr Natalenko
2023-07-31 8:40 ` [PATCH v2 1/3] scsi: qedf: do not touch __user pointer in qedf_dbg_stop_io_on_error_cmd_read() directly Oleksandr Natalenko
2023-07-31 8:40 ` [PATCH v2 2/3] scsi: qedf: do not touch __user pointer in qedf_dbg_debug_cmd_read() directly Oleksandr Natalenko
2023-07-31 8:40 ` [PATCH v2 3/3] scsi: qedf: do not touch __user pointer in qedf_dbg_fp_int_cmd_read() directly Oleksandr Natalenko
2023-07-31 18:33 ` [PATCH v2 0/3] scsi: qedf: sanitise uaccess Laurence Oberman
2023-07-31 18:43 ` Martin K. Petersen
2023-08-01 6:21 ` Oleksandr Natalenko [this message]
2023-08-08 2:50 ` 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=2290359.ElGaqSPkdT@redhat.com \
--to=oleksandr@redhat.com \
--cc=David.Laight@aculab.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=jejb@linux.ibm.com \
--cc=jobacik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=martin.petersen@oracle.com \
--cc=revers@redhat.com \
--cc=skashyap@marvell.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;
as well as URLs for NNTP newsgroup(s).