From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Kees Cook <keescook@chromium.org>,
Larysa Zaremba <larysa.zaremba@intel.com>,
netdev@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-kernel@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
intel-wired-lan@lists.osuosl.org,
linux-hardening@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net-next 0/3] virtchnl: fix fake 1-elem arrays
Date: Fri, 4 Aug 2023 20:09:00 +0200 [thread overview]
Message-ID: <bbf73a71-7ef3-3c43-18aa-bcdeb470a125@intel.com> (raw)
In-Reply-To: <2e163fb1-492e-8a1f-9df1-270c652e9799@intel.com>
From: Tony Nguyen <anthony.l.nguyen@intel.com>
Date: Fri, 4 Aug 2023 11:07:14 -0700
> On 8/4/2023 9:38 AM, Alexander Lobakin wrote:
>> From: Alexander Lobakin <aleksander.lobakin@intel.com>
>> Date: Fri, 28 Jul 2023 17:52:04 +0200
>>
>>> 6.5-rc1 started spitting warning splats when composing virtchnl
>>> messages, precisely on virtchnl_rss_key and virtchnl_lut:
>>>
>>> [ 84.167709] memcpy: detected field-spanning write (size 52) of single
>>> field "vrk->key" at drivers/net/ethernet/intel/iavf/iavf_virtchnl.c:1095
>>> (size 1)
>>> [ 84.169915] WARNING: CPU: 3 PID: 11 at drivers/net/ethernet/intel/
>>> iavf/iavf_virtchnl.c:1095 iavf_set_rss_key+0x123/0x140 [iavf]
>>
>> [...]
>>
>>> .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 9 +-
>>> drivers/net/ethernet/intel/iavf/iavf.h | 6 +-
>>> drivers/net/ethernet/intel/iavf/iavf_client.c | 4 +-
>>> drivers/net/ethernet/intel/iavf/iavf_client.h | 2 +-
>>> .../net/ethernet/intel/iavf/iavf_virtchnl.c | 75 +++++------
>>> drivers/net/ethernet/intel/ice/ice_virtchnl.c | 2 +-
>>> include/linux/avf/virtchnl.h | 127 +++++++++++-------
>>> 7 files changed, 124 insertions(+), 101 deletions(-)
>>>
>>
>> Tony, could you please take it via your next tree? I'd like the
>> validation to make sure more different host <-> guest pairs work.
>>
>> (with Kees' tags, assuming he reviewed and approved the whole series, I
>> asked about #2 already)
>>
>> Thanks,
>> Olek
>
> Ok, will apply it today. For the future if you want it through IWL, can
Great, thanks!
> you tag it with the iwl-* target (and have IWL in the To)? Since this
> had 'net-next' and was 'To' netdev maintainers, I took it that you
> wanted it taken through netdev.
Sure, I know, just for some reason targeted this directly to net at
first, but then realized it would be better for this to go via IWL
:clownface:
>
> Thanks,
> Tony
Thanks,
Olek
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Larysa Zaremba <larysa.zaremba@intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kees Cook <keescook@chromium.org>, <netdev@vger.kernel.org>,
<linux-hardening@vger.kernel.org>,
<intel-wired-lan@lists.osuosl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 0/3] virtchnl: fix fake 1-elem arrays
Date: Fri, 4 Aug 2023 20:09:00 +0200 [thread overview]
Message-ID: <bbf73a71-7ef3-3c43-18aa-bcdeb470a125@intel.com> (raw)
In-Reply-To: <2e163fb1-492e-8a1f-9df1-270c652e9799@intel.com>
From: Tony Nguyen <anthony.l.nguyen@intel.com>
Date: Fri, 4 Aug 2023 11:07:14 -0700
> On 8/4/2023 9:38 AM, Alexander Lobakin wrote:
>> From: Alexander Lobakin <aleksander.lobakin@intel.com>
>> Date: Fri, 28 Jul 2023 17:52:04 +0200
>>
>>> 6.5-rc1 started spitting warning splats when composing virtchnl
>>> messages, precisely on virtchnl_rss_key and virtchnl_lut:
>>>
>>> [ 84.167709] memcpy: detected field-spanning write (size 52) of single
>>> field "vrk->key" at drivers/net/ethernet/intel/iavf/iavf_virtchnl.c:1095
>>> (size 1)
>>> [ 84.169915] WARNING: CPU: 3 PID: 11 at drivers/net/ethernet/intel/
>>> iavf/iavf_virtchnl.c:1095 iavf_set_rss_key+0x123/0x140 [iavf]
>>
>> [...]
>>
>>> .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 9 +-
>>> drivers/net/ethernet/intel/iavf/iavf.h | 6 +-
>>> drivers/net/ethernet/intel/iavf/iavf_client.c | 4 +-
>>> drivers/net/ethernet/intel/iavf/iavf_client.h | 2 +-
>>> .../net/ethernet/intel/iavf/iavf_virtchnl.c | 75 +++++------
>>> drivers/net/ethernet/intel/ice/ice_virtchnl.c | 2 +-
>>> include/linux/avf/virtchnl.h | 127 +++++++++++-------
>>> 7 files changed, 124 insertions(+), 101 deletions(-)
>>>
>>
>> Tony, could you please take it via your next tree? I'd like the
>> validation to make sure more different host <-> guest pairs work.
>>
>> (with Kees' tags, assuming he reviewed and approved the whole series, I
>> asked about #2 already)
>>
>> Thanks,
>> Olek
>
> Ok, will apply it today. For the future if you want it through IWL, can
Great, thanks!
> you tag it with the iwl-* target (and have IWL in the To)? Since this
> had 'net-next' and was 'To' netdev maintainers, I took it that you
> wanted it taken through netdev.
Sure, I know, just for some reason targeted this directly to net at
first, but then realized it would be better for this to go via IWL
:clownface:
>
> Thanks,
> Tony
Thanks,
Olek
next prev parent reply other threads:[~2023-08-04 18:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 15:52 [Intel-wired-lan] [PATCH net-next 0/3] virtchnl: fix fake 1-elem arrays Alexander Lobakin
2023-07-28 15:52 ` Alexander Lobakin
2023-07-28 15:52 ` [Intel-wired-lan] [PATCH net-next 1/3] virtchnl: fix fake 1-elem arrays in structs allocated as `nents + 1` - 1 Alexander Lobakin
2023-07-28 15:52 ` Alexander Lobakin
2023-07-28 22:43 ` [Intel-wired-lan] " Kees Cook
2023-07-28 22:43 ` Kees Cook
2023-08-01 13:08 ` [Intel-wired-lan] " Alexander Lobakin
2023-08-01 13:08 ` Alexander Lobakin
2023-08-04 8:27 ` [Intel-wired-lan] " Kees Cook
2023-08-04 8:27 ` Kees Cook
2023-08-04 15:42 ` [Intel-wired-lan] " Alexander Lobakin
2023-08-04 15:42 ` Alexander Lobakin
2023-08-04 17:29 ` [Intel-wired-lan] " Kees Cook
2023-08-04 17:29 ` Kees Cook
2023-08-04 17:33 ` [Intel-wired-lan] " Alexander Lobakin
2023-08-04 17:33 ` Alexander Lobakin
2023-08-16 12:48 ` [Intel-wired-lan] " Romanowski, Rafal
2023-08-16 12:48 ` Romanowski, Rafal
2023-07-28 15:52 ` [Intel-wired-lan] [PATCH net-next 2/3] virtchnl: fix fake 1-elem arrays in structures allocated as `nents + 1` Alexander Lobakin
2023-07-28 15:52 ` Alexander Lobakin
2023-08-04 8:29 ` [Intel-wired-lan] " Kees Cook
2023-08-04 8:29 ` Kees Cook
2023-08-16 12:49 ` [Intel-wired-lan] " Romanowski, Rafal
2023-08-16 12:49 ` Romanowski, Rafal
2023-07-28 15:52 ` [Intel-wired-lan] [PATCH net-next 3/3] virtchnl: fix fake 1-elem arrays for structures allocated as `nents` Alexander Lobakin
2023-07-28 15:52 ` Alexander Lobakin
2023-08-04 8:30 ` [Intel-wired-lan] " Kees Cook
2023-08-04 8:30 ` Kees Cook
2023-08-16 12:51 ` [Intel-wired-lan] " Romanowski, Rafal
2023-08-16 12:51 ` Romanowski, Rafal
2023-08-03 15:55 ` [Intel-wired-lan] [PATCH net-next 0/3] virtchnl: fix fake 1-elem arrays Alexander Lobakin
2023-08-03 15:55 ` Alexander Lobakin
2023-08-04 16:38 ` [Intel-wired-lan] " Alexander Lobakin
2023-08-04 16:38 ` Alexander Lobakin
2023-08-04 18:07 ` [Intel-wired-lan] " Tony Nguyen
2023-08-04 18:07 ` Tony Nguyen
2023-08-04 18:09 ` Alexander Lobakin [this message]
2023-08-04 18:09 ` Alexander Lobakin
2023-08-16 12:48 ` [Intel-wired-lan] " Romanowski, Rafal
2023-08-16 12:48 ` Romanowski, Rafal
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=bbf73a71-7ef3-3c43-18aa-bcdeb470a125@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.