All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: linux-audit@redhat.com, viro@zeniv.linux.org.uk
Subject: Re: [PATCH] audit: fix size of netlink messages
Date: Mon, 10 Jun 2013 10:50:30 +0200	[thread overview]
Message-ID: <51B59356.4080204@6wind.com> (raw)
In-Reply-To: <20130609132934.GA10805@casper.infradead.org>

Le 09/06/2013 15:29, Thomas Graf a écrit :
> On 06/07/13 at 06:24pm, Nicolas Dichtel wrote:
>> Put Thomas in CC.
>>
>> Le 07/06/2013 17:43, Eric Paris a écrit :
>>> On Fri, 2013-06-07 at 17:25 +0200, Nicolas Dichtel wrote:
>>>
>>> NAK.
>>>
>>> I tried this once before and as I recal userspace actually expected the
>>> stoopidity of being unaligned and broke   :-(
>> On which userspace tools do you think?
>>
>> For example, in the libnl, the function which tries to get the next
>> netlink message expects this alignment:
>
> You should only align the end of the Netlink message if you
> append another Netlink message after it. There is no point
> in aligning it if no message follows in the same buffer.
>
> A receiver should never enforce alignment for the last message.
> Some do and this is causing a lot of pain. An example is the
> Open vSwitch implementation which stricly enforces alignment of
> nlmsg_len which makes attempts to implement zerocopy for the
> upcall more difficult than it should be.
>
Ok, thank you for the clarification.

      parent reply	other threads:[~2013-06-10  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 15:25 [PATCH] audit: fix size of netlink messages Nicolas Dichtel
2013-06-07 15:43 ` Eric Paris
2013-06-07 16:24   ` Nicolas Dichtel
     [not found]     ` <20130609132934.GA10805@casper.infradead.org>
2013-06-10  8:50       ` Nicolas Dichtel [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=51B59356.4080204@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=linux-audit@redhat.com \
    --cc=tgraf@suug.ch \
    --cc=viro@zeniv.linux.org.uk \
    /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.