From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] userns regression fix for v5.12-rc3
Date: Sat, 13 Mar 2021 10:45:36 -0600 [thread overview]
Message-ID: <m1o8fnc89b.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <CAHk-=whw8w_a727dqokA3AsifsMQ2=qZYt1Go8+KCTKczxxSWQ@mail.gmail.com> (Linus Torvalds's message of "Fri, 12 Mar 2021 14:33:38 -0800")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Fri, Mar 12, 2021 at 1:34 PM Eric W. Biederman <ebiederm@xmission.com> wrote:
>>
>> Please pull the for-v5.12-rc3 branch from the git tree.
>>
>> Removing the ambiguity broke userspace so please revert the change:
>> It turns out that there are in fact userspace implementations that
>> care and this recent change caused a regression.
>>
>> https://github.com/containers/buildah/issues/3071
>
> Pulled.
>
> But please cc the kernel mailing list (or something like that) for
> these things, so that you get the pr-tracker-bot reply automatically.
>
> Perhaps you don't care about the pr-tracker-bot that much, but even
> aside from that, I just like the pulls to be cc'd on the lists, if
> only as "documentation".
>
> (Plus since I've gotten used to seeing the pr-tracker-bot
> confirmations, I then get antsy and wondering if something is wrong
> with the bot when it doesn't respond fully when I push things out,
> which is how I noticed this one).
Sorry about that. I meant to CC lkml but my fingers forgot to include
it this time.
I just knew I had to get this out so we could start unbreaking users.
Eric
prev parent reply other threads:[~2021-03-13 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1lfasf44s.fsf@fess.ebiederm.org>
2021-03-12 22:33 ` [GIT PULL] userns regression fix for v5.12-rc3 Linus Torvalds
2021-03-13 16:45 ` Eric W. Biederman [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=m1o8fnc89b.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--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.