linux-kernel - Re: fs/buffer.c: WARNING: alloc_page

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] [day] [month] [year] [list]

Message-ID: <c875cdda-212e-d88c-6456-c270586be1ef@i-love.sakura.ne.jp>
Date:   Thu, 5 Mar 2020 18:49:20 +0900
From:   Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To:     Jan Kara <jack@...e.cz>
Cc:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        linux-fsdevel@...r.kernel.org,
        open list <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Al Viro <viro@...iv.linux.org.uk>,
        Mel Gorman <mgorman@...hsingularity.net>,
        Michal Hocko <mhocko@...nel.org>, ak@...ux.intel.com,
        jlayton@...hat.com, tim.c.chen@...ux.intel.com,
        willy@...radead.org, LTP List <ltp@...ts.linux.it>,
        Jan Stancek <jstancek@...hat.com>, chrubis <chrubis@...e.cz>,
        lkft-triage@...ts.linaro.org,
        Anders Roxell <anders.roxell@...aro.org>
Subject: Re: fs/buffer.c: WARNING: alloc_page_buffers while mke2fs

On 2020/03/05 18:38, Jan Kara wrote:
> On Tue 03-03-20 14:15:24, Naresh Kamboju wrote:
>> [Sorry for the spam]
>>
>> Linux-next 5.6.0-rc3-next-20200302 running on arm64 juno-r2 device while
>> running LTP syscalls chown tests.
>>
>> Suspecting commits are (did not do git bisect),
>> b1473d5f3d0 fs/buffer.c: dump more info for __getblk_gfp() stall problem
>> b10a7ae6565 fs/buffer.c: add debug print for __getblk_gfp() stall problem
> 
> These are almost certainly unrelated. If I'm looking right, the warning is
> coming from memalloc_use_memcg() called from alloc_page_buffers()
> complaining that memcg to charge is already set. But I don't see how that
> would be possible (at least with today's linux-next). Can you reproduce the
> problem with today's linux-next?
> 

Already handled as
https://lore.kernel.org/linux-mm/20200303162948.a383cb88c4a1b0bfd3817798@linux-foundation.org/ .