[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180801151937.GN30522@ZenIV.linux.org.uk>
Date: Wed, 1 Aug 2018 16:19:37 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Kirill Tkhai <ktkhai@...tuozzo.com>
Cc: "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Commit "new primitive: discard_new_inode()" introduces a problem
On Wed, Aug 01, 2018 at 05:43:35PM +0300, Kirill Tkhai wrote:
> Hi, Al,
>
> commit 22dc9a1682722fda8603991595528b87e90436f6
> Author: Al Viro <viro@...iv.linux.org.uk>
> Date: Thu Jun 28 15:53:17 2018 -0400
>
> new primitive: discard_new_inode()
>
> from current linux-next introduces the following problem.
> It reproduces 100% in my test VM:
>
> # cat /etc/mtab
> /dev/sda1 / ext4 rw 0 0
> proc /proc proc rw 0 0
> sysfs /sys sysfs rw 0 0
> devpts /dev/pts devpts rw,gid=5,mode=620 0 0
> tmpfs /dev/shm tmpfs rw,noexec,nosuid,nodev 0 0
> # echo 3 > /proc/sys/vm/drop_caches
> # cat /etc/mtab
> cat: /etc/mtab: Cannot allocate memory
Can't reproduce here... Could you post your .config (and
toolchain information, for the sake of completeness)?
Powered by blists - more mailing lists