From: Dragos Tatulea <dtatulea@nvidia.com>
To: "mst@redhat.com" <mst@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
"linma@zju.edu.cn" <linma@zju.edu.cn>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH 0/2] vdpa: Enable strict validation for netlink ops
Date: Wed, 26 Jul 2023 18:56:24 +0000 [thread overview]
Message-ID: <8a97e0d439d74373605b00dcaef91108ced9e5ee.camel@nvidia.com> (raw)
In-Reply-To: <20230726143640-mutt-send-email-mst@kernel.org>
On Wed, 2023-07-26 at 14:36 -0400, Michael S. Tsirkin wrote:
> On Wed, Jul 26, 2023 at 09:30:48PM +0300, Dragos Tatulea wrote:
> > The original patch from Lin Ma enables the vdpa driver to use validation
> > netlink ops.
> >
> > The second patch simply disables the validation skip which is no longer
> > neccesary. Patchset started of from this discussion [0].
> >
> > [0]
> > https://lore.kernel.org/virtualization/20230726074710-mutt-send-email-mst@kernel.org/T/#t
>
> Cc stable with at least 1/2 ?
>
Sent a v2 with stable in cc. But looks like 1/2 breaks the "fix one thing only"
rule due to the many Fixes tags I guess...
> > Dragos Tatulea (1):
> > vdpa: Enable strict validation for netlinks ops
> >
> > Lin Ma (1):
> > vdpa: Complement vdpa_nl_policy for nlattr length check
> >
> > drivers/vdpa/vdpa.c | 9 +++------
> > 1 file changed, 3 insertions(+), 6 deletions(-)
> >
> > --
> > 2.41.0
>
next prev parent reply other threads:[~2023-07-26 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 18:30 Dragos Tatulea
2023-07-26 18:30 ` [PATCH 1/2] vdpa: Complement vdpa_nl_policy for nlattr length check Dragos Tatulea
2023-07-26 18:30 ` [PATCH 2/2] vdpa: Enable strict validation for netlinks ops Dragos Tatulea
2023-07-26 18:36 ` [PATCH 0/2] vdpa: Enable strict validation for netlink ops Michael S. Tsirkin
2023-07-26 18:56 ` Dragos Tatulea [this message]
2023-07-26 19:23 ` Dragos Tatulea
2023-07-26 19:28 ` Michael S. Tsirkin
2023-07-26 19:28 ` Michael S. Tsirkin
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=8a97e0d439d74373605b00dcaef91108ced9e5ee.camel@nvidia.com \
--to=dtatulea@nvidia.com \
--cc=jasowang@redhat.com \
--cc=linma@zju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®