From: Richard Weinberger <richard.weinberger@gmail.com>
To: Hou Tao <houtao1@huawei.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
Adrian Hunter <ext-adrian.hunter@nokia.com>,
Carson.Li1@unisoc.com
Subject: Re: [PATCH v3 2/2] ubifs: read node from wbuf when it fully sits in wbuf
Date: Mon, 16 Mar 2020 23:33:35 +0100 [thread overview]
Message-ID: <CAFLxGvzrZm=r03VFXWV+=XU_LaVq3XPGeKJxGm-YnV_HHVu_wg@mail.gmail.com> (raw)
In-Reply-To: <20200305092205.127758-3-houtao1@huawei.com>
On Thu, Mar 5, 2020 at 10:15 AM Hou Tao <houtao1@huawei.com> wrote:
> The actual situation of the problem is the LEB is GCed, freed and then
> reused as journal head, and finally ubifs_tnc_locate() reads
> an invalid node. And it can be reproduced by the following steps:
> * create 128 empty files
> * overwrite 8 files in backgroup repeatedly to trigger GC
> * drop inode cache and stat these 128 empty files repeatedly
So far I failed to reproduce. Do you have a script?
Or even better, a xfstest?
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-03-16 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 9:22 [PATCH v3 0/2] fix potential race between ubifs_tnc_locate() and GC Hou Tao
2020-03-05 9:22 ` [PATCH v3 1/2] ubifs: factor out helper ubifs_check_node_buf() Hou Tao
2020-03-05 9:22 ` [PATCH v3 2/2] ubifs: read node from wbuf when it fully sits in wbuf Hou Tao
2020-03-16 22:21 ` Richard Weinberger
2020-07-01 1:15 ` Hou Tao
2020-03-16 22:33 ` Richard Weinberger [this message]
2020-03-18 1:57 ` Hou Tao
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='CAFLxGvzrZm=r03VFXWV+=XU_LaVq3XPGeKJxGm-YnV_HHVu_wg@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=Carson.Li1@unisoc.com \
--cc=ext-adrian.hunter@nokia.com \
--cc=houtao1@huawei.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).