From: Jens Axboe <axboe@kernel.dk>
To: "Michal Koutný" <mkoutny@suse.com>, "Josef Bacik" <josef@toxicpanda.com>
Cc: linux-block@vger.kernel.org, nbd@other.debian.org,
linux-kernel@vger.kernel.org,
Navid Emamdoost <navid.emamdoost@gmail.com>,
Michal Kubecek <mkubecek@suse.cz>
Subject: Re: [PATCH RESEND v3] nbd_genl_status: null check for nla_nest_start
Date: Thu, 23 Mar 2023 16:51:17 -0600 [thread overview]
Message-ID: <6c507b78-35fb-fe23-51f0-e5bb754679d0@kernel.dk> (raw)
In-Reply-To: <20230323193032.28483-1-mkoutny@suse.com>
On 3/23/23 1:30 PM, Michal Koutný wrote:
> From: Navid Emamdoost <navid.emamdoost@gmail.com>
>
> nla_nest_start may fail and return NULL. The check is inserted, and
> errno is selected based on other call sites within the same source code.
> Update: removed extra new line.
> v3 Update: added release reply, thanks to Michal Kubecek for pointing
> out.
Josef? Looks straight forward to me, though it's not clear (to me) how
this can be triggered and hence how important it is.
> Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
> Reviewed-by: Michal Kubecek <mkubecek@suse.cz>
> Link: https://lore.kernel.org/r/20190911164013.27364-1-navid.emamdoost@gmail.com/
> ---
>
> I'm resending the patch because there was apparent consensus of its
> inclusion and it seems it was only overlooked. Some people may care
> about this because of CVE-2019-16089.
Anyone can file a CVE, and in fact they are often filed as some kind
of silly trophy. Whether a CVE exists or not has ZERO bearing on
whether a bug is worth fixing.
So please don't mix CVEs into any of this, they don't matter one bit.
Never have, and never will. What's important is how the bug can be
triggered.
--
Jens Axboe
next prev parent reply other threads:[~2023-03-23 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 19:30 Michal Koutný
2023-03-23 22:51 ` Jens Axboe [this message]
2023-03-24 10:16 ` Michal Koutný
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=6c507b78-35fb-fe23-51f0-e5bb754679d0@kernel.dk \
--to=axboe@kernel.dk \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=mkubecek@suse.cz \
--cc=navid.emamdoost@gmail.com \
--cc=nbd@other.debian.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
all inboxes | Powered by JetHome®