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;
Date:   Sun, 15 Aug 2021 13:42:30 +0200
From:   Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To:     Daniel Borkmann <daniel@iogearbox.net>
Cc:     Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org,
        stable@vger.kernel.org, Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH 5.10 04/19] bpf: Add _kernel suffix to internal
 lockdown_bpf_read
Message-ID: <YRj9pl459cFK+2kJ@kroah.com>
References: <20210813150522.623322501@linuxfoundation.org>
 <20210813150522.774143311@linuxfoundation.org>
 <20210813195523.GA4577@duo.ucw.cz>
 <f42f4fbb-3777-6e5b-0daf-6fdb2cc707b8@iogearbox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f42f4fbb-3777-6e5b-0daf-6fdb2cc707b8@iogearbox.net>
Precedence: bulk

On Fri, Aug 13, 2021 at 11:57:58PM +0200, Daniel Borkmann wrote:
> Hi Pavel,
> 
> On 8/13/21 9:55 PM, Pavel Machek wrote:
> > > From: Daniel Borkmann <daniel@iogearbox.net>
> > > 
> > > commit 71330842ff93ae67a066c1fa68d75672527312fa upstream.
> > > 
> > > Rename LOCKDOWN_BPF_READ into LOCKDOWN_BPF_READ_KERNEL so we have naming
> > > more consistent with a LOCKDOWN_BPF_WRITE_USER option that we are
> > > adding.
> > 
> > As far as I can tell, next bpf patch does not depend on this one and
> > we don't need it in 5.10. (Likely same situation with 5.13).
> 
> Yeah, it's nice to have for consistency given also small as well, but
> also fully okay to drop it as there shouldn't be any conflict.
> 

Ok, now dropped, thanks.

greg k-h