From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
netdev@vger.kernel.org,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Eric Dumazet <edumazet@google.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Simon Horman <horms@kernel.org>, Jakub Kicinski <kuba@kernel.org>,
intel-wired-lan@lists.osuosl.org, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Robert Elliott <elliott@hpe.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v1] ice: fix bug with suspend and rebuild
Date: Thu, 7 Mar 2024 17:11:58 +0100 [thread overview]
Message-ID: <ZennTrYTqsPHylmQ@boxer> (raw)
In-Reply-To: <02751cec-c273-4120-adad-6ea16a86532b@intel.com>
On Wed, Mar 06, 2024 at 05:33:50PM -0800, Jesse Brandeburg wrote:
> On 3/6/2024 8:56 AM, Maciej Fijalkowski wrote:
> > > > Fixes: b3e7b3a6ee92 ("ice: prevent NULL pointer deref during reload")
> > > > Reported-by: Robert Elliott <elliott@hpe.com>
> > > > Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> > >
> > > Reviewed-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> > >
> > > Well, that refactor of config path introduced lots of issues. Could
> > > validation folks include a short list of tests they tried out against
> > > tested patch?
> >
> > Sorry, I got confused and now I saw the same thing Simon pointed out.
>
> Thanks, NP! this thread is for v1, and v2 is already posted with the
> refactor just moving the CONFIG_FOO in patch 1, and then the real final
> version of the fix in v2 patch two which switches all the intel drivers over
> to the new macros.
>
> >
> > >
> > > > ---
> > > > drivers/net/ethernet/intel/ice/ice_lib.c | 16 ++++++++--------
> > > > 1 file changed, 8 insertions(+), 8 deletions(-)
> > > >
> > > > diff --git a/drivers/net/ethernet/intel/ice/ice_lib.c b/drivers/net/ethernet/intel/ice/ice_lib.c
> > > > index 097bf8fd6bf0..0f5a92a6b1e6 100644
> > > > --- a/drivers/net/ethernet/intel/ice/ice_lib.c
> > > > +++ b/drivers/net/ethernet/intel/ice/ice_lib.c
> > > > @@ -3238,7 +3238,7 @@ int ice_vsi_rebuild(struct ice_vsi *vsi, u32 vsi_flags)
> > > > {
> > > > struct ice_vsi_cfg_params params = {};
> > > > struct ice_coalesce_stored *coalesce;
> >
> > struct ice_coalesce_stored *coalesce __free(kfree);
>
> Yes, but not in a "fix" patch for -net. I figure this is more of a refactor
> kind of thing, so will not include it in this change.
I suppose that's because older kernels might not have this construct
backported, so yeah your v2 is good as-is.
>
> >
> > ?
> >
> > and drop explicit kfree()s altogether?
> >
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
"Robert Elliott" <elliott@hpe.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH iwl-net v1] ice: fix bug with suspend and rebuild
Date: Thu, 7 Mar 2024 17:11:58 +0100 [thread overview]
Message-ID: <ZennTrYTqsPHylmQ@boxer> (raw)
In-Reply-To: <02751cec-c273-4120-adad-6ea16a86532b@intel.com>
On Wed, Mar 06, 2024 at 05:33:50PM -0800, Jesse Brandeburg wrote:
> On 3/6/2024 8:56 AM, Maciej Fijalkowski wrote:
> > > > Fixes: b3e7b3a6ee92 ("ice: prevent NULL pointer deref during reload")
> > > > Reported-by: Robert Elliott <elliott@hpe.com>
> > > > Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> > >
> > > Reviewed-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> > >
> > > Well, that refactor of config path introduced lots of issues. Could
> > > validation folks include a short list of tests they tried out against
> > > tested patch?
> >
> > Sorry, I got confused and now I saw the same thing Simon pointed out.
>
> Thanks, NP! this thread is for v1, and v2 is already posted with the
> refactor just moving the CONFIG_FOO in patch 1, and then the real final
> version of the fix in v2 patch two which switches all the intel drivers over
> to the new macros.
>
> >
> > >
> > > > ---
> > > > drivers/net/ethernet/intel/ice/ice_lib.c | 16 ++++++++--------
> > > > 1 file changed, 8 insertions(+), 8 deletions(-)
> > > >
> > > > diff --git a/drivers/net/ethernet/intel/ice/ice_lib.c b/drivers/net/ethernet/intel/ice/ice_lib.c
> > > > index 097bf8fd6bf0..0f5a92a6b1e6 100644
> > > > --- a/drivers/net/ethernet/intel/ice/ice_lib.c
> > > > +++ b/drivers/net/ethernet/intel/ice/ice_lib.c
> > > > @@ -3238,7 +3238,7 @@ int ice_vsi_rebuild(struct ice_vsi *vsi, u32 vsi_flags)
> > > > {
> > > > struct ice_vsi_cfg_params params = {};
> > > > struct ice_coalesce_stored *coalesce;
> >
> > struct ice_coalesce_stored *coalesce __free(kfree);
>
> Yes, but not in a "fix" patch for -net. I figure this is more of a refactor
> kind of thing, so will not include it in this change.
I suppose that's because older kernels might not have this construct
backported, so yeah your v2 is good as-is.
>
> >
> > ?
> >
> > and drop explicit kfree()s altogether?
> >
>
>
next prev parent reply other threads:[~2024-03-07 16:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 23:08 [Intel-wired-lan] [PATCH iwl-net v1] ice: fix bug with suspend and rebuild Jesse Brandeburg
2024-03-04 23:08 ` Jesse Brandeburg
2024-03-05 6:28 ` [Intel-wired-lan] " Paul Menzel
2024-03-05 6:28 ` Paul Menzel
2024-03-05 13:17 ` Simon Horman
2024-03-05 13:17 ` Simon Horman
2024-03-05 17:35 ` [Intel-wired-lan] " Jesse Brandeburg
2024-03-05 17:35 ` Jesse Brandeburg
2024-03-06 16:46 ` [Intel-wired-lan] " Maciej Fijalkowski
2024-03-06 16:46 ` Maciej Fijalkowski
2024-03-06 16:56 ` [Intel-wired-lan] " Maciej Fijalkowski
2024-03-06 16:56 ` Maciej Fijalkowski
2024-03-07 1:33 ` [Intel-wired-lan] " Jesse Brandeburg
2024-03-07 1:33 ` Jesse Brandeburg
2024-03-07 1:41 ` [Intel-wired-lan] " Jesse Brandeburg
2024-03-07 1:41 ` Jesse Brandeburg
2024-03-07 16:10 ` [Intel-wired-lan] " Maciej Fijalkowski
2024-03-07 16:10 ` Maciej Fijalkowski
2024-03-07 16:11 ` Maciej Fijalkowski [this message]
2024-03-07 16:11 ` Maciej Fijalkowski
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=ZennTrYTqsPHylmQ@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elliott@hpe.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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.