From: David Miller <davem@davemloft.net>
To: xemul@openvz.org
Cc: akpm@linux-foundation.org, tgraf@suug.ch, eparis@parisplace.org,
dwmw2@infradead.org, viro@zeniv.linux.org.uk,
linux-audit@redhat.com, linux-kernel@vger.kernel.org,
sgrubb@redhat.com, amy.griffis@hp.com
Subject: Re: [PATCH] audit: netlink socket can be auto-bound to pid other than current->pid (v2)
Date: Thu, 20 Mar 2008 15:39:58 -0700 (PDT) [thread overview]
Message-ID: <20080320.153958.81546591.davem@davemloft.net> (raw)
In-Reply-To: <47E25F7F.5040907@openvz.org>
From: Pavel Emelyanov <xemul@openvz.org>
Date: Thu, 20 Mar 2008 15:58:39 +0300
> This patch is based on the one from Thomas.
..
> Signed-off-by: Thomas Graf <tgraf@suug.ch>
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
> Acked-by: Eric Paris <eparis@redhat.com>
Applied, thanks everyone.
prev parent reply other threads:[~2008-03-20 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 12:58 [PATCH] audit: netlink socket can be auto-bound to pid other than current->pid (v2) Pavel Emelyanov
2008-03-20 22:39 ` David Miller [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=20080320.153958.81546591.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=amy.griffis@hp.com \
--cc=dwmw2@infradead.org \
--cc=eparis@parisplace.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sgrubb@redhat.com \
--cc=tgraf@suug.ch \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@openvz.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