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]
Message-ID: <9eb3efe1-f203-c3b1-679d-5e158fd8639f@linux.alibaba.com>
Date:   Fri, 6 Mar 2020 12:42:03 +0800
From:   Alex Shi <alex.shi@...ux.alibaba.com>
To:     Hugh Dickins <hughd@...gle.com>, Qian Cai <cai@....pw>
Cc:     Matthew Wilcox <willy@...radead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>, aarcange@...hat.com,
        daniel.m.jordan@...cle.com, hannes@...xchg.org,
        khlebnikov@...dex-team.ru, kirill@...temov.name,
        kravetz@...ibm.com, mhocko@...nel.org, mm-commits@...r.kernel.org,
        tj@...nel.org, vdavydov.dev@...il.com, yang.shi@...ux.alibaba.com,
        linux-mm@...ck.org
Subject: Re: [failures] mm-vmscan-remove-unnecessary-lruvec-adding.patch
 removed from -mm tree



在 2020/3/6 下午12:17, Hugh Dickins 写道:
> On Thu, 5 Mar 2020, Qian Cai wrote:
>>> On Mar 5, 2020, at 10:38 PM, Matthew Wilcox <willy@...radead.org> wrote:
>>>
>>> On Thu, Mar 05, 2020 at 10:32:18PM -0500, Qian Cai wrote:
>>>>> On Mar 5, 2020, at 9:50 PM, akpm@...ux-foundation.org wrote:
>>>>> The patch titled
>>>>>    Subject: mm/vmscan: remove unnecessary lruvec adding
>>>>> has been removed from the -mm tree.  Its filename was
>>>>>    mm-vmscan-remove-unnecessary-lruvec-adding.patch
>>>>>
>>>>> This patch was dropped because it had testing failures
>>>> Andrew, do you have more information about this failure? I hit a bug
>>>> here under memory pressure and am wondering if this is related
>>>> which might save me some time digging…
> Very likely related.
> 

Hi all,

Apologize for the trouble!
And Many thanks for you all for the report!
Obviously, I missed memory stress testing which I should do. Apologize again!

Qian Cai,
Which test case are you using? Could you share the reproduce steps for me?

Hugh,
Many thanks for help! I will seek some memory stress case and waiting for your case.


Thank you all!
Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ