From: David Laight <David.Laight@ACULAB.COM>
To: linux-sctp@vger.kernel.org
Subject: RE: packed structures used in socket options
Date: Sun, 07 Jun 2020 13:53:18 +0000 [thread overview]
Message-ID: <ec8c26c792ea414dbe50bda45725d26f@AcuMS.aculab.com> (raw)
In-Reply-To: <CBFEFEF1-127A-4ADA-B438-B171B9E26282@lurchi.franken.de>
From: Michael Tuexen
>
> since gcc uses -Werrordress-of-packed-member, I get warnings for my variant
> of packetdrill, which supports SCTP.
>
> Here is why:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/sctp.h?h=v5
> .7
> contains:
>
> struct sctp_paddrparams {
> sctp_assoc_t spp_assoc_id;
> struct sockaddr_storage spp_address;
> __u32 spp_hbinterval;
> __u16 spp_pathmaxrxt;
> __u32 spp_pathmtu;
> __u32 spp_sackdelay;
> __u32 spp_flags;
> __u32 spp_ipv6_flowlabel;
> __u8 spp_dscp;
> } __attribute__((packed, aligned(4)));
>
> This structure is only used in the IPPROTO_SCTP level socket option SCTP_PEER_ADDR_PARAMS.
> Why is it packed?
I'm guessing 'to remove holes to avoid leaking kernel data'.
The sctp socket api defines loads of structures that will have
holes in them if not packed.
OTOH they shouldn't have been packed either.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-06-07 13:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 10:49 packed structures used in socket options Michael Tuexen
2020-06-07 13:53 ` David Laight [this message]
2020-06-07 15:15 ` Michael Tuexen
2020-06-07 17:14 ` David Laight
2020-06-07 17:23 ` Michael Tuexen
2020-06-07 20:21 ` David Laight
2020-06-07 21:35 ` Ivan Skytte Jørgensen
2020-06-08 16:18 ` David Laight
2020-06-08 16:18 ` David Laight
2020-06-08 17:37 ` Michael Tuexen
2020-06-08 17:37 ` Michael Tuexen
2020-06-08 21:13 ` David Laight
2020-06-08 21:13 ` David Laight
2020-06-07 21:51 ` Michael Tuexen
2020-06-08 8:17 ` David Laight
2020-06-08 8:17 ` David Laight
2020-06-07 21:55 ` Michael Tuexen
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=ec8c26c792ea414dbe50bda45725d26f@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=linux-sctp@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 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.