From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
<linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ata: libata-scsi: fix sloppy result type of ata_ioc32()
Date: Mon, 20 Jun 2022 23:26:47 +0300 [thread overview]
Message-ID: <e8dcebdc-7618-533e-0050-dd03ef1f4bb8@omp.ru> (raw)
In-Reply-To: <d653908c-1270-9c2f-eceb-2572e9c9d339@opensource.wdc.com>
On 6/20/22 2:12 AM, Damien Le Moal wrote:
>> While ata_ioc32() returns *int*, its result gets assigned to and compared
>> with the *unsigned long* variable 'val' in ata_sas_scsi_ioctl(), its only
>> caller, which implies a problematic implicit cast -- fix that by returning
>> *unsigned long* instead.
>>
>> Found by Linux Verification Center (linuxtesting.org) with the SVACE static
>> analysis tool.
>>
>> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
>>
>> ---
>> This patch is against the 'for-next' branch of Damien's 'libata.git' repo.
>>
>> drivers/ata/libata-scsi.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> Index: libata/drivers/ata/libata-scsi.c
>> ===================================================================
>> --- libata.orig/drivers/ata/libata-scsi.c
>> +++ libata/drivers/ata/libata-scsi.c
>> @@ -539,7 +539,7 @@ int ata_task_ioctl(struct scsi_device *s
>> return rc;
>> }
>>
>> -static int ata_ioc32(struct ata_port *ap)
>> +static unsigned long ata_ioc32(struct ata_port *ap)
>> {
>> if (ap->flags & ATA_FLAG_PIO_DMA)
>> return 1;
> Actually, this should be a bool I think and the ioctl code cleaned to use
By the ioctl code you mean ata_sas_scsi_ioctl()?
> that type since the val argument of the ioctl is also used as a bool.
As for HDIO_SET_32BIT, that's prolly OK but what to do with HDIO_GET_32BIT
(it calls put_user() on *unsigned long*)?
MBR, Sergey
next prev parent reply other threads:[~2022-06-20 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 19:30 [PATCH] ata: libata-scsi: fix sloppy result type of ata_ioc32() Sergey Shtylyov
2022-06-19 23:12 ` Damien Le Moal
2022-06-20 20:26 ` Sergey Shtylyov [this message]
2022-06-20 22:44 ` Damien Le Moal
2022-06-21 19:14 ` Sergey Shtylyov
2022-06-21 20:37 ` Sergey Shtylyov
2022-06-21 22:15 ` Damien Le Moal
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=e8dcebdc-7618-533e-0050-dd03ef1f4bb8@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@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