From: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>, Jan Kara <jack@suse.cz>
Subject: ext4: Fix use after free issues with journalled data
Date: Tue, 21 Apr 2020 10:54:42 +0200 [thread overview]
Message-ID: <20200421085445.5731-1-jack@suse.cz> (raw)
Hello,
this series of patches fixes possible use-after-free issues resulting from
freed inode being still in writeback list. One partner was able to trigger
this using fsstress on filesystem on pmem device. The first patch fixes
mostly a theoretical issue, the third patch fixes a real issue happening
in the wild and leading to kernel crashing.
Honza
next reply other threads:[~2020-04-21 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 8:54 Jan Kara [this message]
2020-04-21 8:54 ` [PATCH 1/3] fs: Avoid leaving freed inode on dirty list Jan Kara
2020-04-25 6:42 ` Xiaoguang Wang
2020-04-27 10:05 ` Jan Kara
2020-04-21 8:54 ` [PATCH 2/3] writeback: Export inode_io_list_del() Jan Kara
2020-05-14 14:57 ` Theodore Y. Ts'o
2020-04-21 8:54 ` [PATCH 3/3] ext4: Avoid freeing inodes on dirty list Jan Kara
2020-05-14 14:57 ` Theodore Y. Ts'o
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=20200421085445.5731-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=tytso@mit.edu \
/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