lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 25 Feb 2021 14:12:52 +0100
From:   David Sterba <dsterba@...e.cz>
To:     Ira Weiny <ira.weiny@...el.com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        David Sterba <dsterba@...e.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>
Subject: Re: [GIT PULL] Kmap conversions for 5.12

On Wed, Feb 24, 2021 at 09:59:12AM -0800, Ira Weiny wrote:
> On Wed, Feb 24, 2021 at 01:30:49PM +0100, David Sterba wrote:
> > On Tue, Feb 23, 2021 at 11:25:06AM -0800, Ira Weiny wrote:
> > > On Tue, Feb 23, 2021 at 09:13:42AM -0800, Linus Torvalds wrote:
> > > > On Tue, Feb 23, 2021 at 7:03 AM David Sterba <dsterba@...e.com> wrote:
> > [...]
> > 
> > > Sorry.  I will change it.
> > 
> > Let me know how you want to proceed with the patchset/pull request.
> 
> To be clear I'd like to just drop the 2 patches which use zero_user() for this
> merge window.
> 
> I've already submitted some additional btrfs changes for 5.13[1].  I can rework
> these zero_user() patches and submit them through Andrew for 5.13 as separate
> set.  That is what I meant by 'I will change it'.
> 
> > I
> > can play the messenger again but now it seems a round of review is
> > needed and with some testing it'll be possible in some -rc. At that
> > point you may take the patches via the mm tree, unless Linus is ok with
> > a late pull.
> 
> I'm ok with delaying the memzero_page() change to 5.13.  There are a lot of
> kmap changes to come.  But I'm trying to do them as smaller series just for
> this reason.  I don't want valid changes to be denied due to my messing up just
> a few patches...  :-(  Hopefully you and Linus can forgive me on this one.
> 
> Is ok to just drop them and merge the rest of this series in 5.12?

Ok, no problem. Please let me know exactly which patches to drop, I'll
respin the branch. Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ