From: Jens Axboe <axboe@kernel.dk>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Scott Bauer <scott.bauer@intel.com>
Cc: hch@infradead.org, linux-block@vger.kernel.org,
Scott Bauer <sbauer@plzdonthack.me>,
stable@vger.kernel.org
Subject: Re: [PATCH] cdrom: Fix info leak/OOB read in cdrom_ioctl_drive_status
Date: Wed, 29 Aug 2018 08:09:46 -0600 [thread overview]
Message-ID: <46b669b9-e31f-54a6-dcd6-10e5b7f30406@kernel.dk> (raw)
In-Reply-To: <20180829124842.plpsjdvausmtikhj@mwanda>
On 8/29/18 6:48 AM, Dan Carpenter wrote:
> Sorry, I responded to this patch that this wasn't a real bug, but then
> Scott corrected me that it was.
>
> Anyway, it is a bug and we haven't applied this patch yet.
It is now, apparently I lost track of it too. Thanks Scott.
--
Jens Axboe
prev parent reply other threads:[~2018-08-29 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 17:51 [PATCH] cdrom: Fix info leak/OOB read in cdrom_ioctl_drive_status Scott Bauer
2018-04-27 12:41 ` Dan Carpenter
2018-04-27 14:43 ` Scott Bauer
2018-04-27 15:13 ` Dan Carpenter
2018-08-29 12:48 ` Dan Carpenter
2018-08-29 14:09 ` 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=46b669b9-e31f-54a6-dcd6-10e5b7f30406@kernel.dk \
--to=axboe@kernel.dk \
--cc=dan.carpenter@oracle.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=sbauer@plzdonthack.me \
--cc=scott.bauer@intel.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