linux-kernel - RE: [PATCH 1/2] include: uapi: scsi: Change utp_upiu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BY5PR04MB632701F87296BEE554D3F055EDAD9@BY5PR04MB6327.namprd04.prod.outlook.com>
Date:   Wed, 1 Mar 2023 09:46:59 +0000
From:   Arthur Simchaev <Arthur.Simchaev@....com>
To:     Bart Van Assche <bvanassche@....org>,
        "martin.petersen@...cle.com" <martin.petersen@...cle.com>
CC:     "beanhuo@...ron.com" <beanhuo@...ron.com>,
        "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/2] include: uapi: scsi: Change utp_upiu_query struct

> >>>   struct utp_upiu_query {
> >>>     __u8 opcode;
> >>>     __u8 idn;
> >>>     __u8 index;
> >>>     __u8 selector;
> >>> -   __be16 reserved_osf;
> >>> -   __be16 length;
> >>> -   __be32 value;
> >>> -   __be32 reserved[2];
> >>> +   __u8 osf3;
> >>> +   __u8 osf4;
> >>> +   __be16 osf5;
> >>> +   __be32 osf6;
> >>> +   __be32 osf7;
> >>>   };
> >> All changes in UAPI headers must be backwards compatible. The above
> doesn't look like a backwards compatible change to me.
> >
> > This API was originally invented to support ufs-bsg.
> > AFAIK, ufs-utils is the only app that makes use of this API,
> > and it doesn't dig into struct utp_upiu_query inner fields.
> 
> That does not match what I see. I see that code in ufs-utils accesses
> the 'length' and 'value' members of the above data structure.
> 
> Please follow the rules for UAPI header files.
> 
> Thanks,
> 
> Bart.

You are right , my fault.
Anyway, It just return reserved field to the struct.
Also I can update the tool accordingly. Instead length and value fields,
using osf5 and osf6.
In this case we will keep it backward compatible.
Is it OK?

Regards
Arthur

> -----Original Message-----
> From: Bart Van Assche <bvanassche@....org>
> Sent: Monday, February 27, 2023 7:00 PM
> To: Arthur Simchaev <Arthur.Simchaev@....com>;
> martin.petersen@...cle.com
> Cc: beanhuo@...ron.com; linux-scsi@...r.kernel.org; linux-
> kernel@...r.kernel.org
> Subject: Re: [PATCH 1/2] include: uapi: scsi: Change utp_upiu_query struct
> 
> CAUTION: This email originated from outside of Western Digital. Do not click
> on links or open attachments unless you recognize the sender and know that
> the content is safe.
> 
> 
> On 2/27/23 08:03, Arthur Simchaev wrote:
> >>>
> >>>    */
> >>>   struct utp_upiu_query {
> >>>     __u8 opcode;
> >>>     __u8 idn;
> >>>     __u8 index;
> >>>     __u8 selector;
> >>> -   __be16 reserved_osf;
> >>> -   __be16 length;
> >>> -   __be32 value;
> >>> -   __be32 reserved[2];
> >>> +   __u8 osf3;
> >>> +   __u8 osf4;
> >>> +   __be16 osf5;
> >>> +   __be32 osf6;
> >>> +   __be32 osf7;
> >>>   };
> >> All changes in UAPI headers must be backwards compatible. The above
> doesn't look like a backwards compatible change to me.
> >
> > This API was originally invented to support ufs-bsg.
> > AFAIK, ufs-utils is the only app that makes use of this API,
> > and it doesn't dig into struct utp_upiu_query inner fields.
> 
> That does not match what I see. I see that code in ufs-utils accesses
> the 'length' and 'value' members of the above data structure.
> 
> Please follow the rules for UAPI header files.
> 
> Thanks,
> 
> Bart.