From: David Miller <davem@davemloft.net>
To: JBeulich@suse.com
Cc: paul.durrant@citrix.com, wei.liu2@citrix.com,
xen-devel@lists.xenproject.org, netdev@vger.kernel.org
Subject: Re: Ping: [PATCH 0/3] xen-netback: hash mapping hanling adjustments
Date: Mon, 24 Sep 2018 09:49:20 -0700 (PDT) [thread overview]
Message-ID: <20180924.094920.655625438524720848.davem@davemloft.net> (raw)
In-Reply-To: <5BA895B602000078001EB059@prv1-mh.provo.novell.com>
From: "Jan Beulich" <JBeulich@suse.com>
Date: Mon, 24 Sep 2018 01:43:50 -0600
>>>> On 11.09.18 at 12:16, <wei.liu2@citrix.com> wrote:
>> On Tue, Sep 11, 2018 at 02:12:07AM -0600, Jan Beulich wrote:
>>> >>> On 28.08.18 at 16:54, wrote:
>>> > First and foremost the fix for XSA-270. On top of that further changes
>>> > which looked desirable to me while investigating that XSA.
>>> >
>>> > 1: fix input validation in xenvif_set_hash_mapping()
>>> > 2: validate queue numbers in xenvif_set_hash_mapping()
>>> > 3: handle page straddling in xenvif_set_hash_mapping()
>>> >
>>> > Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>>
>>> What is the way forward here? I've got R-b-s from Paul for all three
>>> patches, and a minor change request on patch 2 from Wei. I'm not
>>> really certain what to do in this case (hints appreciated), but could
>>> at least the security fix (patch 1) be applied immediately?
>>
>> If you happen to resend, please make the adjustment; otherwise I'm fine
>> with the patches as they are. I don't want to block useful things on
>> cosmetic issues.
>
> Dave? I notice none of the patches is in 4.19-rc5, not even the security
> fix, the advisory for which had gone public over a month ago.
If it's not in my patchwork queue, you have to resend the series and
make it clear that it should be applied to the networking tree by
putting "[PATCH net N/M]" in the Subject lines.
Thank you.
next prev parent reply other threads:[~2018-09-24 22:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 14:54 [PATCH 0/3] xen-netback: hash mapping hanling adjustments Jan Beulich
2018-08-28 14:59 ` [PATCH 1/3] xen-netback: fix input validation in xenvif_set_hash_mapping() Jan Beulich
2018-08-28 14:59 ` [PATCH 2/3] xen-netback: validate queue numbers " Jan Beulich
2018-08-29 8:25 ` Wei Liu
2018-09-03 9:23 ` Paul Durrant
2018-08-28 15:00 ` [PATCH 3/3] xen-netback: handle page straddling " Jan Beulich
2018-08-29 8:26 ` Wei Liu
2018-09-03 9:28 ` Paul Durrant
2018-09-11 8:12 ` [PATCH 0/3] xen-netback: hash mapping hanling adjustments Jan Beulich
2018-09-11 10:16 ` Wei Liu
2018-09-24 7:43 ` Ping: " Jan Beulich
2018-09-24 16:49 ` David Miller [this message]
[not found] ` <C61B6A85020000F18A491530@prv1-mh.provo.novell.com>
2018-09-25 8:18 ` Jan Beulich
2018-09-25 8:11 ` [PATCH net 0/3 RESEND] xen-netback: hash mapping handling adjustments Jan Beulich
2018-09-25 17:40 ` David Miller
2018-09-25 8:12 ` [PATCH net 1/3 RESEND] xen-netback: fix input validation in xenvif_set_hash_mapping() Jan Beulich
2018-09-25 8:13 ` [PATCH net 2/3 RESEND] xen-netback: validate queue numbers " Jan Beulich
2018-09-25 8:13 ` [PATCH net 3/3 RESEND] xen-netback: handle page straddling " Jan Beulich
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=20180924.094920.655625438524720848.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=JBeulich@suse.com \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).