From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
Daniel Machon <daniel.machon@microchip.com>,
netdev@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Dave Ertman <david.m.ertman@intel.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net] ice: fix unaligned access in ice_create_lag_recipe
Date: Fri, 2 Feb 2024 14:00:03 +0100 [thread overview]
Message-ID: <ZbznU+j2b4OIcDgb@boxer> (raw)
In-Reply-To: <15af160b-54b1-4f27-ad72-01fc27601f69@intel.com>
On Fri, Feb 02, 2024 at 01:40:18PM +0100, Alexander Lobakin wrote:
> From: Alexander Lobakin <aleksander.lobakin@intel.com>
> Date: Fri, 2 Feb 2024 13:39:28 +0100
>
> > From: Michal Schmidt <mschmidt@redhat.com>
> > Date: Thu, 1 Feb 2024 19:40:17 +0100
> >
> >> On 1/31/24 17:59, Alexander Lobakin wrote:
> >>> From: Jiri Pirko <jiri@resnulli.us>
> >>> Date: Wed, 31 Jan 2024 13:17:44 +0100
> >>>
> >>>> Wed, Jan 31, 2024 at 12:58:23PM CET, mschmidt@redhat.com wrote:
> >>>>> diff --git a/drivers/net/ethernet/intel/ice/ice_lag.c
> >>>>> b/drivers/net/ethernet/intel/ice/ice_lag.c
> >>>>> index 2a25323105e5..d4848f6fe919 100644
> >>>>> --- a/drivers/net/ethernet/intel/ice/ice_lag.c
> >>>>> +++ b/drivers/net/ethernet/intel/ice/ice_lag.c
> >>>>> @@ -1829,9 +1829,7 @@ static int ice_create_lag_recipe(struct ice_hw
> >>>>> *hw, u16 *rid,
> >>>>> new_rcp->content.act_ctrl_fwd_priority = prio;
> >>>>> new_rcp->content.rid = *rid | ICE_AQ_RECIPE_ID_IS_ROOT;
> >>>>> new_rcp->recipe_indx = *rid;
> >>>>> - bitmap_zero((unsigned long *)new_rcp->recipe_bitmap,
> >>>>> - ICE_MAX_NUM_RECIPES);
> >>>>> - set_bit(*rid, (unsigned long *)new_rcp->recipe_bitmap);
> >>>>> + put_unaligned_le64(BIT_ULL(*rid), new_rcp->recipe_bitmap);
> >>>>
> >>>> Looks like there might be another incorrect bitmap usage for this in
> >>>> ice_add_sw_recipe(). Care to fix it there as well?
> >>>
> >>> Those are already fixed in one switchdev series and will be sent to IWL
> >>> soon.
> >>> I believe this patch would also make no sense after it's sent.
> >>
> >> Hi Alexander,
> >> When will the series be sent?
> >> The bug causes a kernel panic. Will the series target net.git?
> >
> > The global fix is here: [0]
> > It's targeting net-next.
> >
> > I don't know what the best way here would be. Target net instead or pick
> > your fix to net and then fix it properly in net-next?
>
> Sorry, forgot to paste the link :clownface:
IMHO 1/2 should go to net. Then you would have to wait for it to got
accepted and get merged to -next and then you come back with 2/2. You know
the deal.
>
> [0]
> https://lore.kernel.org/intel-wired-lan/20240130025146.30265-2-steven.zou@intel.com
>
> Thanks,
> Olek
>
WARNING: multiple messages have this Message-ID (diff)
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: Michal Schmidt <mschmidt@redhat.com>,
Jiri Pirko <jiri@resnulli.us>,
Daniel Machon <daniel.machon@microchip.com>,
<netdev@vger.kernel.org>,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Dave Ertman <david.m.ertman@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net] ice: fix unaligned access in ice_create_lag_recipe
Date: Fri, 2 Feb 2024 14:00:03 +0100 [thread overview]
Message-ID: <ZbznU+j2b4OIcDgb@boxer> (raw)
In-Reply-To: <15af160b-54b1-4f27-ad72-01fc27601f69@intel.com>
On Fri, Feb 02, 2024 at 01:40:18PM +0100, Alexander Lobakin wrote:
> From: Alexander Lobakin <aleksander.lobakin@intel.com>
> Date: Fri, 2 Feb 2024 13:39:28 +0100
>
> > From: Michal Schmidt <mschmidt@redhat.com>
> > Date: Thu, 1 Feb 2024 19:40:17 +0100
> >
> >> On 1/31/24 17:59, Alexander Lobakin wrote:
> >>> From: Jiri Pirko <jiri@resnulli.us>
> >>> Date: Wed, 31 Jan 2024 13:17:44 +0100
> >>>
> >>>> Wed, Jan 31, 2024 at 12:58:23PM CET, mschmidt@redhat.com wrote:
> >>>>> diff --git a/drivers/net/ethernet/intel/ice/ice_lag.c
> >>>>> b/drivers/net/ethernet/intel/ice/ice_lag.c
> >>>>> index 2a25323105e5..d4848f6fe919 100644
> >>>>> --- a/drivers/net/ethernet/intel/ice/ice_lag.c
> >>>>> +++ b/drivers/net/ethernet/intel/ice/ice_lag.c
> >>>>> @@ -1829,9 +1829,7 @@ static int ice_create_lag_recipe(struct ice_hw
> >>>>> *hw, u16 *rid,
> >>>>> new_rcp->content.act_ctrl_fwd_priority = prio;
> >>>>> new_rcp->content.rid = *rid | ICE_AQ_RECIPE_ID_IS_ROOT;
> >>>>> new_rcp->recipe_indx = *rid;
> >>>>> - bitmap_zero((unsigned long *)new_rcp->recipe_bitmap,
> >>>>> - ICE_MAX_NUM_RECIPES);
> >>>>> - set_bit(*rid, (unsigned long *)new_rcp->recipe_bitmap);
> >>>>> + put_unaligned_le64(BIT_ULL(*rid), new_rcp->recipe_bitmap);
> >>>>
> >>>> Looks like there might be another incorrect bitmap usage for this in
> >>>> ice_add_sw_recipe(). Care to fix it there as well?
> >>>
> >>> Those are already fixed in one switchdev series and will be sent to IWL
> >>> soon.
> >>> I believe this patch would also make no sense after it's sent.
> >>
> >> Hi Alexander,
> >> When will the series be sent?
> >> The bug causes a kernel panic. Will the series target net.git?
> >
> > The global fix is here: [0]
> > It's targeting net-next.
> >
> > I don't know what the best way here would be. Target net instead or pick
> > your fix to net and then fix it properly in net-next?
>
> Sorry, forgot to paste the link :clownface:
IMHO 1/2 should go to net. Then you would have to wait for it to got
accepted and get merged to -next and then you come back with 2/2. You know
the deal.
>
> [0]
> https://lore.kernel.org/intel-wired-lan/20240130025146.30265-2-steven.zou@intel.com
>
> Thanks,
> Olek
>
next prev parent reply other threads:[~2024-02-02 13:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 11:58 [Intel-wired-lan] [PATCH net] ice: fix unaligned access in ice_create_lag_recipe Michal Schmidt
2024-01-31 11:58 ` Michal Schmidt
2024-01-31 12:17 ` [Intel-wired-lan] " Jiri Pirko
2024-01-31 12:17 ` Jiri Pirko
2024-01-31 16:59 ` [Intel-wired-lan] " Alexander Lobakin
2024-01-31 16:59 ` Alexander Lobakin
2024-02-01 18:40 ` Michal Schmidt
2024-02-01 18:40 ` Michal Schmidt
2024-02-02 12:39 ` Alexander Lobakin
2024-02-02 12:39 ` Alexander Lobakin
2024-02-02 12:40 ` Alexander Lobakin
2024-02-02 12:40 ` Alexander Lobakin
2024-02-02 12:54 ` Jiri Pirko
2024-02-02 12:54 ` Jiri Pirko
2024-02-02 13:00 ` Maciej Fijalkowski [this message]
2024-02-02 13:00 ` Maciej Fijalkowski
2024-02-02 13:01 ` Alexander Lobakin
2024-02-02 13:01 ` Alexander Lobakin
2024-02-07 0:44 ` Zou, Steven
2024-02-07 0:44 ` Zou, Steven
2024-02-07 2:15 ` Zou, Steven
2024-02-07 2:15 ` Zou, Steven
2025-01-08 3:09 ` Hongchen Zhang
2025-01-08 3:09 ` Hongchen Zhang
2025-01-08 8:59 ` [Intel-wired-lan] " Przemek Kitszel
2025-01-08 8:59 ` Przemek Kitszel
2025-01-09 1:54 ` [Intel-wired-lan] " Hongchen Zhang
2025-01-09 1:54 ` Hongchen Zhang
2025-01-09 9:31 ` [Intel-wired-lan] " Przemek Kitszel
2025-01-09 9:31 ` Przemek Kitszel
2025-01-09 15:56 ` [Intel-wired-lan] " Alexander Lobakin
2025-01-09 15:56 ` Alexander Lobakin
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=ZbznU+j2b4OIcDgb@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=daniel.machon@microchip.com \
--cc=david.m.ertman@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--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 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.