linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jason Yan <yanaijie@huawei.com>,
	viro@zeniv.linux.org.uk, axboe@kernel.dk,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
	Jan Kara <jack@suse.cz>, Hulk Robot <hulkci@huawei.com>
Subject: Re: [PATCH v4] block: Fix use-after-free in blkdev_get()
Date: Mon, 8 Jun 2020 08:47:11 +0200	[thread overview]
Message-ID: <CA+icZUUks4oJGJLhiRLTJTzyNxfsT_TZQ12MMvBVLXSaR8t0zA@mail.gmail.com> (raw)
In-Reply-To: <20200608061502.GB17366@lst.de>

On Mon, Jun 8, 2020 at 8:18 AM Christoph Hellwig <hch@lst.de> wrote:
>
> Looks good,
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> Can you dig into the history for a proper fixes tag?

[ CC Dan ]

Dan gave the hint for the Fixes: tag in reply to the first patch:

> The Fixes tag is a good idea though:
>
> Fixes: 89e524c04fa9 ("loop: Fix mount(2) failure due to race with LOOP_SET_FD")

> It broke last July.  Before that, we used to check if __blkdev_get()
> failed before dereferencing "bdev".

- Sedat -

  parent reply	other threads:[~2020-06-08  6:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08  2:05 [PATCH v4] block: Fix use-after-free in blkdev_get() Jason Yan
2020-06-08  6:15 ` Christoph Hellwig
2020-06-08  6:43   ` Jason Yan
2020-06-08  6:47   ` Sedat Dilek [this message]
2020-06-08  6:52     ` Sedat Dilek
2020-06-08  7:09       ` Sedat Dilek
2020-06-08  9:48 Markus Elfring
2020-06-08 11:26 ` Christoph Hellwig
2020-06-09  9:12 ` Greg KH

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=CA+icZUUks4oJGJLhiRLTJTzyNxfsT_TZQ12MMvBVLXSaR8t0zA@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=hulkci@huawei.com \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yanaijie@huawei.com \
    /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).