From: Jens Axboe <axboe@kernel.dk>
To: Omar Sandoval <osandov@osandov.com>, Jens Axboe <axboe@fb.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
linux-block@vger.kernel.org, kernel-team@fb.com,
stable@vger.kernel.org
Subject: Re: [PATCH] block: fix use-after-free in sys_ioprio_get()
Date: Fri, 1 Jul 2016 08:39:52 -0600 [thread overview]
Message-ID: <577680B8.4020003@kernel.dk> (raw)
In-Reply-To: <fa9c9a3ee7355f932d4f40322602aae5fb293f97.1467358615.git.osandov@fb.com>
On 07/01/2016 01:39 AM, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> get_task_ioprio() accesses the task->io_context without holding the task
> lock and thus can race with exit_io_context(), leading to a
> use-after-free. The reproducer below hits this within a few seconds on
> my 4-core QEMU VM:
Thanks Omar, applied for this series.
--
Jens Axboe
prev parent reply other threads:[~2016-07-01 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 7:39 [PATCH] block: fix use-after-free in sys_ioprio_get() Omar Sandoval
2016-07-01 14:39 ` Jens Axboe [this message]
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=577680B8.4020003@kernel.dk \
--to=axboe@kernel.dk \
--cc=axboe@fb.com \
--cc=dvyukov@google.com \
--cc=kernel-team@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=stable@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 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).