Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <m1lfasf44s.fsf@fess.ebiederm.org>
In-Reply-To: <m1lfasf44s.fsf@fess.ebiederm.org>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri, 12 Mar 2021 14:33:38 -0800
Message-ID: <CAHk-=whw8w_a727dqokA3AsifsMQ2=qZYt1Go8+KCTKczxxSWQ@mail.gmail.com>
Subject: Re: [GIT PULL] userns regression fix for v5.12-rc3
To:     "Eric W. Biederman" <ebiederm@xmission.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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).

              Linus