From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: tytso@mit.edu, bpm@sgi.com, jlbec@evilplan.org
Subject: [PATCH 0/4] Fix possible use after free with AIO
Date: Wed, 23 Jan 2013 13:56:16 +0100 [thread overview]
Message-ID: <1358945780-23661-1-git-send-email-jack@suse.cz> (raw)
Hi,
when simplifying ext4 IO completion code I realized that the only
thing pinning inode while AIO is running is file reference from kiocb.
Thus once aio_complete() is called, inode can be freed. So calling
inode_dio_complete() after aio_complete() is possibly modifying
already freed inode (although practically the race window is tiny).
This patch series fixes all the problematic sites. Patches are
completely independent so each of them can go through the respective
maintainer.
Honza
next reply other threads:[~2013-01-23 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 12:56 Jan Kara [this message]
2013-01-23 12:56 ` [PATCH 1/4] ext4: Fix possible use-after-free with AIO Jan Kara
2013-01-23 13:18 ` Carlos Maiolino
2013-01-23 12:56 ` [PATCH 2/4] xfs: " Jan Kara
2013-01-23 22:00 ` Ben Myers
2013-01-23 12:56 ` [PATCH 3/4] ocfs2: " Jan Kara
2013-01-23 12:56 ` [PATCH 4/4] fs: " Jan Kara
2013-01-23 15:02 ` Jeff Moyer
2013-01-23 19:18 ` Jan Kara
2013-01-23 16:03 ` [PATCH 0/4] Fix possible use after free " Jeff Moyer
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=1358945780-23661-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=bpm@sgi.com \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).