From: Denis Efremov <efremov@linux.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Willy Tarreau <w@1wt.eu>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] floppy: suppress UBSAN warning in setup_rw_floppy()
Date: Wed, 22 Apr 2020 11:32:40 +0300 [thread overview]
Message-ID: <b1bae333-fe86-2c48-b872-fb72ebe2d53e@linux.com> (raw)
In-Reply-To: <20200422082400.GA30239@infradead.org>
On 4/22/20 11:24 AM, Christoph Hellwig wrote:
>
> I don't think we can just change FD_RAW_CMD_SIZE or cmd as that could
> break userspace.
The second patch adds these defines FD_RAW_CMD_SIZE, FD_RAW_REPLY_SIZE.
Currently they are not in the uapi. Ok, I will send v2.
But otherwise, yes something very much like that:
>
>> #define FD_RAW_CMD_SIZE 16
>> #define FD_RAW_REPLY_SIZE 16
>> +#define FD_RAW_FULL_CMD_SIZE (FD_RAW_CMD_SIZE + 1 + FD_RAW_CMD_SIZE)
>>
>> unsigned char cmd_count;
>> - unsigned char cmd[FD_RAW_CMD_SIZE];
>> - unsigned char reply_count;
>> - unsigned char reply[FD_RAW_REPLY_SIZE];
>> + union {
>> + struct {
>> + unsigned char cmd[FD_RAW_CMD_SIZE];
>> + unsigned char reply_count;
>> + unsigned char reply[FD_RAW_REPLY_SIZE];
>> + };
>> + unsigned char full_cmd[FD_RAW_FULL_CMD_SIZE];
>> + };
>
>> int track;
>>
>> Denis
> ---end quoted text---
>
prev parent reply other threads:[~2020-04-22 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 12:57 [PATCH 0/3] floppy: suppress UBSAN warning in setup_rw_floppy() Denis Efremov
2020-04-21 12:57 ` [PATCH 1/3] floppy: add FD_AUTODETECT_SIZE define for struct floppy_drive_params Denis Efremov
2020-04-21 12:57 ` [PATCH 2/3] floppy: add defines for sizes of cmd & reply buffers of floppy_raw_cmd Denis Efremov
2020-04-21 12:57 ` [PATCH 3/3] floppy: suppress UBSAN warning in setup_rw_floppy() Denis Efremov
2020-04-22 7:09 ` Christoph Hellwig
2020-04-22 7:17 ` Willy Tarreau
2020-04-22 8:20 ` Denis Efremov
2020-04-22 8:24 ` Christoph Hellwig
2020-04-22 8:32 ` Denis Efremov [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=b1bae333-fe86-2c48-b872-fb72ebe2d53e@linux.com \
--to=efremov@linux.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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.