From: David Miller <davem@davemloft.net>
To: keescook@chromium.org
Cc: linux-kernel@vger.kernel.org, santosh@chelsio.com,
netdev@vger.kernel.org, agordeev@redhat.com, joe@perches.com
Subject: Re: [PATCH] cxgb3: avoid needless buffer copy for firmware
Date: Sun, 21 Jun 2015 09:50:54 -0700 (PDT) [thread overview]
Message-ID: <20150621.095054.1961985059600092774.davem@davemloft.net> (raw)
In-Reply-To: <20150616223617.GA17958@www.outflux.net>
From: Kees Cook <keescook@chromium.org>
Date: Tue, 16 Jun 2015 15:36:17 -0700
> There's no reason to perform a buffer copy for the firmware name. This
> also avoids a (currently impossible with current callers) NULL dereference
> if there was no matching firmware.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
Applied to net-next, thanks.
prev parent reply other threads:[~2015-06-21 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 22:36 [PATCH] cxgb3: avoid needless buffer copy for firmware Kees Cook
2015-06-21 16:50 ` David Miller [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=20150621.095054.1961985059600092774.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=agordeev@redhat.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=santosh@chelsio.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).