Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Cc: netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
	Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
	Jacob Keller <jacob.e.keller@intel.com>,
	Jakub Kicinski <kuba@kernel.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 NULL pointer access during resume
Date: Thu, 22 Feb 2024 14:10:17 -0800	[thread overview]
Message-ID: <481ea432-154a-b3c3-73ad-4a5ab6fe25ba@intel.com> (raw)
In-Reply-To: <20240220231720.14836-1-jesse.brandeburg@intel.com>

On 2/20/2024 3:17 PM, Jesse Brandeburg wrote:
> The ice_suspend/ice_resume cycle was not updated when refactoring was
> done to the init path and I suspect this allowed a bug to creep in where
> the driver was not correctly reinitialized during resume.
> 
> I was able to test against 6.1.77 kernel and that ice driver works fine
> for suspend/resume with no panic.
> 
> Instead of tearing down interrupts and freeing a bunch of memory during
> suspend, just begin an internal reset event, which takes care of all the
> correct steps during suspend.  Likewise during resume we'll just let the
> reset complete and the driver comes right back to life. This mirrors the
> behavior of other suspend/resume code in drivers like fm10k.
> 
> Older kernel commits were made to this driver and to the i40e driver to
> try to fix "disk" or hibernate suspend events with many CPUs. The PM
> subsystem was updated since then but the drivers kept the old flows.
> Testing with rtcwake -m [disk | mem] -s 10 - passes but my system won't
> hibernate due to too much RAM, not enough swap.
> 
> The code is slightly refactored during this change in order to share a
> common "prep" path between suspend and the pci error handler functions
> which all do the same thing, so introduce ice_quiesce_before_reset().
> 
> While doing all this and compile testing I ran across the pm.h changes
> to get rid of compilation problems when CONFIG_PM=n etc, so those small
> changes are included here as well.
> 

...

> 
> Fixes: 5b246e533d01 ("ice: split probe into smaller functions")
> Reported-by: Robert Elliott <elliott@hpe.com>
> Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> ---
> NOTE:
> Requires Amritha's patch:
> https://patchwork.ozlabs.org/project/intel-wired-lan/patch/170785373072.3325.9129916579186572531.stgit@anambiarhost.jf.intel.com/
> to be applied before this will pass testing cleanly.

I think this may be the other way around? It looks to be clean for 
netdev (doesn't have Amritha's patch), but it's not applying to 
net-queue (has Amritha's patch).

 > base-commit: 23f9c2c066e7e5052406fb8f04a115d3d0260b22

Base commit also seems to be a netdev commit.

Since Amritha's patch is pending to netdev [1], I think we need a 
version that will apply with Amritha's changes.

Thanks,
Tony


[1] 
https://lore.kernel.org/netdev/20240220214444.1039759-7-anthony.l.nguyen@intel.com/

  reply	other threads:[~2024-02-22 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 23:17 [Intel-wired-lan] [PATCH iwl-net v1] ice: fix NULL pointer access during resume Jesse Brandeburg
2024-02-22 22:10 ` Tony Nguyen [this message]
2024-02-22 22:19   ` Keller, Jacob E
2024-02-22 22:25     ` Tony Nguyen
2024-02-23  1:04       ` Jesse Brandeburg

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=481ea432-154a-b3c3-73ad-4a5ab6fe25ba@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=elliott@hpe.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=michal.swiatkowski@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox