From: David Kozub <zub@linux.fjfi.cvut.cz>
To: Jens Axboe <axboe@kernel.dk>,
Jonathan Derrick <jonathan.derrick@intel.com>,
Scott Bauer <sbauer@plzdonthack.me>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jonas Rabenstein <jonas.rabenstein@studium.uni-erlangen.de>
Subject: Re: [PATCH 1/3] block: sed-opal: add ioctl for done-mark of shadow mbr
Date: Wed, 1 May 2019 12:36:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1905010145240.19150@linux.fjfi.cvut.cz> (raw)
In-Reply-To: <1556666459-17948-2-git-send-email-zub@linux.fjfi.cvut.cz>
On Wed, 1 May 2019, David Kozub wrote:
> @@ -104,6 +109,12 @@ struct opal_mbr_data {
> __u8 __align[7];
> };
>
> +struct opal_mbr_done {
> + struct opal_key key;
> + __u8 done_flag;
> + __u8 __align[7];
> +};
While I just copied opal_mbr_data here, I wonder what is the point of
__align in these structs. By itself it just pads the structure to have a
size that is a multiple of 8. Is this to make sure that anything that lies
past the structure is 8-bytes aligned (assuming the start is 8-bytes
aligned too), perhaps for 32bit userspace with 64bit kernel?
And if it's this, is it needed for these IOCTL structs? (I can see it
being useful for struct opal_key.)
Best regards,
David
next prev parent reply other threads:[~2019-05-01 10:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 23:20 [PATCH 0/3] block: sed-opal: add support for shadow MBR done flag and write David Kozub
2019-04-30 23:20 ` [PATCH 1/3] block: sed-opal: add ioctl for done-mark of shadow mbr David Kozub
2019-05-01 10:36 ` David Kozub [this message]
2019-05-01 13:46 ` Christoph Hellwig
2019-05-05 14:16 ` Scott Bauer
2019-05-06 20:02 ` Derrick, Jonathan
2019-04-30 23:20 ` [PATCH 2/3] block: sed-opal: ioctl for writing to " David Kozub
2019-05-01 13:48 ` Christoph Hellwig
2019-05-05 14:22 ` Scott Bauer
2019-04-30 23:20 ` [PATCH 3/3] block: sed-opal: check size of " David Kozub
2019-05-05 14:27 ` Scott Bauer
2019-05-06 20:15 ` Derrick, Jonathan
2019-05-01 13:49 ` [PATCH 0/3] block: sed-opal: add support for shadow MBR done flag and write Christoph Hellwig
2019-05-03 20:32 ` David Kozub
2019-05-05 14:43 ` Scott Bauer
2019-05-09 19:31 ` Derrick, Jonathan
2019-05-13 22:12 ` David Kozub
2019-05-02 12:30 ` Scott Bauer
2019-05-02 16:03 ` David Kozub
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=alpine.LRH.2.21.1905010145240.19150@linux.fjfi.cvut.cz \
--to=zub@linux.fjfi.cvut.cz \
--cc=axboe@kernel.dk \
--cc=jonas.rabenstein@studium.uni-erlangen.de \
--cc=jonathan.derrick@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sbauer@plzdonthack.me \
/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
all inboxes | Powered by JetHome®