From: Jan Kara <jack@suse.cz>
To: Hillf Danton <hdanton@sina.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org,
syzbot+d79afb004be235636ee8@syzkaller.appspotmail.com,
linux-fsdevel@vger.kernel.org, linux-nilfs@vger.kernel.org,
Ryusuke Konishi <konishi.ryusuke@gmail.com>
Subject: Re: [RFC PATCH] mm: truncate: flush lru cache for evicted inode
Date: Mon, 17 Jun 2024 09:57:58 +0200 [thread overview]
Message-ID: <20240617075758.wewhukbrjod5fp5o@quack3> (raw)
In-Reply-To: <20240616023951.1250-1-hdanton@sina.com>
On Sun 16-06-24 10:39:51, Hillf Danton wrote:
> On Sat, 15 Jun 2024 21:44:54 +0100 Matthew Wilcox wrote:
> >
> > I suspect this would trigger:
> >
> > +++ b/fs/inode.c
> > @@ -282,6 +282,7 @@ static struct inode *alloc_inode(struct super_block *sb)
> > void __destroy_inode(struct inode *inode)
> > {
> > BUG_ON(inode_has_buffers(inode));
> > + BUG_ON(inode->i_data.nrpages);
> > inode_detach_wb(inode);
> > security_inode_free(inode);
> > fsnotify_inode_delete(inode);
> >
> Yes, it was triggered [1]
>
> [1] https://lore.kernel.org/lkml/00000000000084b401061af6ab80@google.com/
>
> and given trigger after nrpages is checked in clear_inode(),
>
> iput(inode)
> evict(inode)
> truncate_inode_pages_final(&inode->i_data);
> clear_inode(inode);
> destroy_inode(inode);
>
> why is folio added to exiting mapping?
>
> #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 83a7eefedc9b
OK, so based on syzbot results this seems to be a bug in
nilfs_evict_inode() (likely caused by corrupted filesystem so that root
inode's link count was 0 and hence was getting deleted on iput()). I guess
nilfs maintainers need to address these with more consistency checks of
metadata when loading them...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-06-17 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 13:18 Hillf Danton
2024-06-14 13:42 ` Matthew Wilcox
2024-06-14 23:59 ` Hillf Danton
2024-06-15 20:44 ` Matthew Wilcox
2024-06-15 23:52 ` Hillf Danton
2024-06-16 0:10 ` [syzbot] [nilfs?] [mm?] KASAN: slab-use-after-free Read in lru_add_fn syzbot
2024-06-16 2:39 ` [RFC PATCH] mm: truncate: flush lru cache for evicted inode Hillf Danton
2024-06-16 3:06 ` [syzbot] [nilfs?] [mm?] KASAN: slab-use-after-free Read in lru_add_fn syzbot
2024-06-17 7:57 ` Jan Kara [this message]
2024-06-17 11:24 ` [RFC PATCH] mm: truncate: flush lru cache for evicted inode Ryusuke Konishi
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=20240617075758.wewhukbrjod5fp5o@quack3 \
--to=jack@suse.cz \
--cc=hdanton@sina.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=syzbot+d79afb004be235636ee8@syzkaller.appspotmail.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox