From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kaber@trash.net
Subject: Re: [PATCH] af_packet: prevent information leak
Date: Tue, 07 Jun 2011 07:41:31 +0200 [thread overview]
Message-ID: <1307425291.2642.66.camel@edumazet-laptop> (raw)
In-Reply-To: <1307425119.2642.63.camel@edumazet-laptop>
Le mardi 07 juin 2011 à 07:38 +0200, Eric Dumazet a écrit :
> It should not matter for these structures, or 393e52e33c6c2 would have
> break applications on all arches (not only ARM), since it enlarged them
> without any warning ;)
>
>
>
BTW, it means that next time we want to add a field in these structure,
we cant use the padding space, or else an application cant know for sure
if the kernel put a padding (say on linux-3.0) or the new field
(linux-3.8)
next prev parent reply other threads:[~2011-06-07 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 5:02 [PATCH] af_packet: prevent information leak Eric Dumazet
2011-06-07 5:24 ` David Miller
2011-06-07 5:38 ` Eric Dumazet
2011-06-07 5:41 ` Eric Dumazet [this message]
2011-06-07 5:42 ` David Miller
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=1307425291.2642.66.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@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