From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: jasowang@redhat.com, stefanha@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] vhost: fix OOB in get_rx_bufs()
Date: Tue, 29 Jan 2019 20:36:31 -0500 [thread overview]
Message-ID: <20190129203157-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190129.153810.493942539151548676.davem@davemloft.net>
On Tue, Jan 29, 2019 at 03:38:10PM -0800, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Tue, 29 Jan 2019 15:10:26 -0800 (PST)
>
> > Yeah the CVE pushed my hand a little bit, and I knew I was going to
> > send Linus a pull request today because David Watson needs some TLS
> > changes in net-next.
>
> I also want to make a general comment.... for the record.
>
> If I let patches slip consistently past 24 hours my backlog is
> unmanageable. Even with aggressively applying things quickly I'm
> right now at 70-75. If I do not do what I am doing, then it's in the
> 100-150 range.
>
> So I am at the point where I often must move forward with patches that
> I think I personally can verify and vet on my own.
If it helps I can include most virtio stuff in my pull requests instead.
Or if that can't work since there's too often a dependency on net-next,
maybe Jason wants to create a tree and send pull requests to you. Let
us know if that will help, and which of the options looks better from
your POV.
--
MST
next prev parent reply other threads:[~2019-01-30 1:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 7:05 [PATCH net] vhost: fix OOB in get_rx_bufs() Jason Wang
2019-01-29 6:30 ` Stefan Hajnoczi
2019-01-29 6:30 ` Stefan Hajnoczi
2019-01-29 6:54 ` David Miller
2019-01-29 6:54 ` David Miller
2019-01-29 22:54 ` Michael S. Tsirkin
2019-01-29 23:10 ` David Miller
2019-01-29 23:38 ` David Miller
2019-01-30 1:36 ` Michael S. Tsirkin
2019-01-30 1:36 ` Michael S. Tsirkin [this message]
2019-01-30 22:31 ` David Miller
2019-01-30 22:31 ` David Miller
2019-01-29 23:38 ` David Miller
2019-01-29 23:10 ` David Miller
2019-01-29 22:54 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2019-01-28 7:05 Jason Wang
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=20190129203157-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.