From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: New Coverity defect in BPF verifier
Date: Mon, 22 May 2017 10:26:43 -0700 [thread overview]
Message-ID: <20170522102643.35a02b7d@xeon-e3> (raw)
In-Reply-To: <20170522.121604.2157216252893063658.davem@davemloft.net>
On Mon, 22 May 2017 12:16:04 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> Stephen, if you had even lightly scanned netdev today, you can see
> that we are discussing this already and there are at least two
> patches proposed.
>
> Thank you.
Sorry hadn't gotten that far. Doing full scan of 100's of messages
a day is not always possible.
prev parent reply other threads:[~2017-05-22 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 16:05 New Coverity defect in BPF verifier Stephen Hemminger
2017-05-22 16:16 ` David Miller
2017-05-22 17:26 ` Stephen Hemminger [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=20170522102643.35a02b7d@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=netdev@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).