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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201012230550.GB19671@intel.com>
Date:   Tue, 13 Oct 2020 07:05:50 +0800
From:   Philip Li <philip.li@...el.com>
To:     Roman Gushchin <guro@...com>
Cc:     kernel test robot <lkp@...el.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        kbuild-all@...ts.01.org, LKML <linux-kernel@...r.kernel.org>,
        Bastian Bittorf <bb@....de>, Vlastimil Babka <vbabka@...e.cz>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux Memory Management List <linux-mm@...ck.org>,
        Shakeel Butt <shakeelb@...gle.com>
Subject: Re: [kbuild-all] Re: [PATCH] mm: memcg/slab: fix slab statistics in
 !SMP configuration

On Fri, Oct 02, 2020 at 10:55:06AM -0700, Roman Gushchin wrote:
> On Fri, Oct 02, 2020 at 01:34:06PM +0800, Philip Li wrote:
> > On Thu, Oct 01, 2020 at 05:55:59PM -0700, Roman Gushchin wrote:
> > > On Fri, Oct 02, 2020 at 08:08:40AM +0800, kbuild test robot wrote:
> > > > Hi Roman,
> > > > 
> > > > Thank you for the patch! Yet something to improve:
> > > > 
> > > > [auto build test ERROR on mmotm/master]
> > > 
> > > It's a bogus error, the patch was applied onto mmotm/master, which doesn't
> > > contain necessary slab controller patches.
> > sorry for the wrong report, and thanks for the input, we will check
> > this to see whether we can find an appropriate base for this case.
> 
> I wonder if you can look at the "Fixes" tag if the patch contains one?
Thanks for the advice. Yes, we have Fixes tag as part of hint for us
to analzye the possible base. For this case, "Fixes: ea426c2", the commit sha
is a little short than we expected, thus ignored. We have updated matching
rule now to handle such situation.

> 
> > Meanwhile, you can give a try to use --base option when git format patch, which
> > helps us to have more clue when looking for base info.
> 
> Will do.
> 
> Thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ