From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v3 0/3] Fixes for scsi_mode_sense/select()
Date: Wed, 29 Sep 2021 00:15:00 -0400 [thread overview]
Message-ID: <yq1lf3gdns5.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20210820070255.682775-1-damien.lemoal@wdc.com> (Damien Le Moal's message of "Fri, 20 Aug 2021 16:02:52 +0900")
Damien,
> The first patch in this series is the formet standalone patch titled
> "scsi: fix scsi_mode_sense()". Patch 2 fixes similar buffer length
> handling problems found in scsi_mode_select().
> Patch 3 fixes the use of scsi_mode_sense() in sd.c to ensure that calls
> are issued with a sensible buffer size for devices that explicitly
> requested the use of MODE SENSE 10 (e.g. SATA drives on AHCI).
Applied to 5.16/scsi-staging with some changes. There was some confusion
between SENSE vs. SELECT in patch #2 in particular.
I tried to clean up the dbd situation a while back but it fell by the
wayside:
https://lore.kernel.org/all/20200325222416.5094-1-martin.petersen@oracle.com/
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2021-09-29 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 7:02 [PATCH v3 0/3] Fixes for scsi_mode_sense/select() Damien Le Moal
2021-08-20 7:02 ` [PATCH v3 1/3] scsi: fix scsi_mode_sense() buffer length handling Damien Le Moal
2021-08-20 7:02 ` [PATCH v3 2/3] scsi: fix scsi_mode_select() " Damien Le Moal
2021-08-20 7:02 ` [PATCH v3 3/3] scsi: sd: fix sd_do_mode_sense() " Damien Le Moal
2021-09-29 4:15 ` Martin K. Petersen [this message]
2021-09-29 6:02 ` [PATCH v3 0/3] Fixes for scsi_mode_sense/select() Damien Le Moal
2021-10-05 4:34 ` 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=yq1lf3gdns5.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=damien.lemoal@wdc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox