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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 21 May 2020 11:35:49 +0200 From: Arnd Bergmann <arnd@...db.de> To: Naresh Kamboju <naresh.kamboju@...aro.org> Cc: Chris Down <chris@...isdown.name>, Yafang Shao <laoar.shao@...il.com>, Michal Hocko <mhocko@...nel.org>, Anders Roxell <anders.roxell@...aro.org>, "Linux F2FS DEV, Mailing List" <linux-f2fs-devel@...ts.sourceforge.net>, linux-ext4 <linux-ext4@...r.kernel.org>, linux-block <linux-block@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, open list <linux-kernel@...r.kernel.org>, Linux-Next Mailing List <linux-next@...r.kernel.org>, linux-mm <linux-mm@...ck.org>, Andreas Dilger <adilger.kernel@...ger.ca>, Jaegeuk Kim <jaegeuk@...nel.org>, "Theodore Ts'o" <tytso@....edu>, Chao Yu <chao@...nel.org>, Hugh Dickins <hughd@...gle.com>, Andrea Arcangeli <aarcange@...hat.com>, Matthew Wilcox <willy@...radead.org>, Chao Yu <yuchao0@...wei.com>, lkft-triage@...ts.linaro.org, Johannes Weiner <hannes@...xchg.org>, Roman Gushchin <guro@...com>, Cgroups <cgroups@...r.kernel.org> Subject: Re: mm: mkfs.ext4 invoked oom-killer on i386 - pagecache_get_page On Thu, May 21, 2020 at 11:22 AM Naresh Kamboju <naresh.kamboju@...aro.org> wrote: > On Thu, 21 May 2020 at 00:39, Chris Down <chris@...isdown.name> wrote: > > Since you have i386 hardware available, and I don't, could you please apply > > only "avoid stale protection" again and check if it only happens with that > > commit, or requires both? That would help narrow down the suspects. Note that Naresh is running an i386 kernel on regular 64-bit hardware that most people have access to. > kernel config link, > https://builds.tuxbuild.com/8lg6WQibcwtQRRtIa0bcFA/kernel.config Do you know if the same bug shows up running a kernel with that configuration in qemu? I would expect it to, and that would make it much easier to reproduce. I would also not be surprised if it happens on all architectures but only shows up on the 32-bit arm and x86 machines first because they have a rather limited amount of lowmem. Maybe booting a 64-bit kernel with "mem=512M" and then running "dd if=/dev/sda of=/dev/null bs=1M" will also trigger it. I did not attempt to run this myself. Arnd
Powered by blists - more mailing lists