All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Kirill Tkhai <ktkhai@virtuozzo.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Commit "new primitive: discard_new_inode()" introduces a problem
Date: Wed, 1 Aug 2018 16:19:37 +0100	[thread overview]
Message-ID: <20180801151937.GN30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <64a0f022-a32d-d4ee-7464-5c5ce0ebd222@virtuozzo.com>

On Wed, Aug 01, 2018 at 05:43:35PM +0300, Kirill Tkhai wrote:
> Hi, Al,
> 
> commit 22dc9a1682722fda8603991595528b87e90436f6
> Author: Al Viro <viro@zeniv.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)?

  reply	other threads:[~2018-08-01 17:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 14:43 Commit "new primitive: discard_new_inode()" introduces a problem Kirill Tkhai
2018-08-01 15:19 ` Al Viro [this message]
2018-08-01 15:43   ` Kirill Tkhai
2018-08-01 16:11     ` Al Viro
2018-08-01 16:16       ` Al Viro
2018-08-01 16:19         ` Kirill Tkhai
2018-08-01 16:34           ` Al Viro
2018-08-02  3:14             ` Rafael David Tinoco
2018-08-02  7:43             ` Kirill Tkhai
2018-08-01 16:27         ` Al Viro
2018-08-02  2:36           ` Rafael David Tinoco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180801151937.GN30522@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.