From: ebiederm@xmission.com (Eric W. Biederman)
To: Eric Paris <eparis@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
David Miller <davem@davemloft.net>,
rgb@redhat.com, linux-audit@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] namespaces fixes for 3.14-rcX
Date: Mon, 10 Mar 2014 12:56:06 -0700 [thread overview]
Message-ID: <87r469rfop.fsf@xmission.com> (raw)
In-Reply-To: <1394459944.17193.12.camel@localhost> (Eric Paris's message of "Mon, 10 Mar 2014 09:59:04 -0400")
Eric Paris <eparis@redhat.com> writes:
> On Sun, 2014-03-09 at 20:06 -0700, Eric W. Biederman wrote:
>> My efforts to get these fixes noticed by people who care about audit
>> seem to have landed on deaf ears, so since these are namespace related I
>> have put them in my tree.
>
> This commentary sounds like a pile of crap seeing as how there was a
> whole discussion around how to handle this stuff, which you were a part
> of. And that the audit tree already picked up these 2 patches.
My apologies for offending. Last night when I looked the audit tree had
not been updated in 7 weeks, and Andrew Morton wasn't ready to push
these fixes to Linus and was looking for someone who would. Keeping
important bug fixes in my retransmit queue leaves me very grumpy.
> In any case, since I haven't sent them to Linus and I'm glad that is
> done, so feel free to consider this me Acking the pull request.
Eric
next prev parent reply other threads:[~2014-03-10 19:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 18:49 [PATCH] audit: Use struct net not pid_t to remember the network namespce to reply in Eric W. Biederman
2014-02-28 18:49 ` Eric W. Biederman
2014-03-01 1:11 ` Richard Guy Briggs
2014-03-01 4:34 ` Eric W. Biederman
2014-03-01 4:36 ` [PATCH] audit: Send replies in the proper network namespace Eric W. Biederman
2014-03-01 4:50 ` [RFC][PATCH] audit: Simplify by assuming the callers socket buffer is large enough Eric W. Biederman
2014-03-01 4:50 ` Eric W. Biederman
2014-03-04 21:30 ` Andrew Morton
2014-03-04 21:30 ` Andrew Morton
2014-03-04 21:51 ` David Miller
2014-03-04 22:41 ` Eric W. Biederman
2014-03-04 22:50 ` Andrew Morton
2014-03-04 22:50 ` Andrew Morton
2014-03-10 3:06 ` [GIT PULL] namespaces fixes for 3.14-rcX Eric W. Biederman
2014-03-10 13:59 ` Eric Paris
2014-03-10 19:56 ` Eric W. Biederman [this message]
2014-03-16 18:36 ` Richard Guy Briggs
2014-03-05 0:21 ` [RFC][PATCH] audit: Simplify by assuming the callers socket buffer is large enough David Miller
2014-03-05 16:59 ` Steve Grubb
2014-03-05 16:59 ` Steve Grubb
2014-03-05 17:57 ` LC Bruzenak
2014-03-05 18:06 ` Eric W. Biederman
2014-03-07 22:52 ` Eric Paris
2014-03-08 0:48 ` David Miller
2014-03-08 3:27 ` Steve Grubb
2014-03-08 6:34 ` David Miller
2014-03-08 6:34 ` David Miller
2014-03-08 3:56 ` Eric Paris
2014-03-10 19:30 ` David Miller
2014-03-10 21:57 ` Eric Paris
2014-03-10 21:57 ` Eric Paris
2014-03-16 18:19 ` [PATCH] audit: Send replies in the proper network namespace Richard Guy Briggs
2014-03-16 19:13 ` Richard Guy Briggs
2014-03-16 18:15 ` [PATCH] audit: Use struct net not pid_t to remember the network namespce to reply in Richard Guy Briggs
2014-03-16 19:12 ` Richard Guy Briggs
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=87r469rfop.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rgb@redhat.com \
--cc=torvalds@linux-foundation.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.