All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: Marcin Szycik <marcin.szycik@linux.intel.com>
Cc: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
	intel-wired-lan@lists.osuosl.org,
	himasekharx.reddy.pucha@intel.com, pmenzel@molgen.mpg.de,
	marcin.szycik@intel.com, netdev@vger.kernel.org,
	rafal.romanowski@intel.com, konrad.knitter@intel.com,
	pawel.chmielewski@intel.com, horms@kernel.org,
	David.Laight@aculab.com, nex.sw.ncis.nat.hpm.dev@intel.com,
	pio.raczynski@gmail.com, sridhar.samudrala@intel.com,
	jacob.e.keller@intel.com, jiri@resnulli.us,
	przemyslaw.kitszel@intel.com,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] [iwl-next v9 5/9] ice, irdma: move interrupts code to irdma
Date: Fri, 14 Feb 2025 06:41:35 +0100	[thread overview]
Message-ID: <Z67XjwByeVSuLooq@mev-dev.igk.intel.com> (raw)
In-Reply-To: <8e533834-4564-472f-b29b-4f1cb7730053@linux.intel.com>

On Thu, Feb 13, 2025 at 08:20:31PM +0100, Marcin Szycik wrote:
> 
> 
> On 03.12.2024 07:58, Michal Swiatkowski wrote:
> > Move responsibility of MSI-X requesting for RDMA feature from ice driver
> > to irdma driver. It is done to allow simple fallback when there is not
> > enough MSI-X available.
> > 
> > Change amount of MSI-X used for control from 4 to 1, as it isn't needed
> > to have more than one MSI-X for this purpose.
> 
> Hi, I'm observing KASAN reports or kernel panic when attempting to remove irdma
> with this patchset, most probably this patch being the culprit, since it touches
> functions from splat.
> 
> Reproducer:
>   sudo rmmod irdma
> 
> Minified splat(s):
>   BUG: KASAN: use-after-free in irdma_remove+0x257/0x2d0 [irdma]
>   Call Trace:
>    <TASK>
>    ? __pfx__raw_spin_lock_irqsave+0x10/0x10
>    ? kfree+0x253/0x450
>    ? irdma_remove+0x257/0x2d0 [irdma]
>    kasan_report+0xed/0x120
>    ? irdma_remove+0x257/0x2d0 [irdma]
>    irdma_remove+0x257/0x2d0 [irdma]
>    auxiliary_bus_remove+0x56/0x80
>    device_release_driver_internal+0x371/0x530
>    ? kernfs_put.part.0+0x147/0x310
>    driver_detach+0xbf/0x180
>    bus_remove_driver+0x11b/0x2a0
>    auxiliary_driver_unregister+0x1a/0x50
>    irdma_exit_module+0x40/0x4c [irdma]
>   
>   Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI
>   KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
>   RIP: 0010:ice_free_rdma_qvector+0x2a/0xa0 [ice]
>   Call Trace:
>    ? ice_free_rdma_qvector+0x2a/0xa0 [ice]
>    irdma_remove+0x179/0x2d0 [irdma]
>    auxiliary_bus_remove+0x56/0x80
>    device_release_driver_internal+0x371/0x530
>    ? kobject_put+0x61/0x4b0
>    driver_detach+0xbf/0x180
>    bus_remove_driver+0x11b/0x2a0
>    auxiliary_driver_unregister+0x1a/0x50
>    irdma_exit_module+0x40/0x4c [irdma]

Thanks, I will work on it.

> 

  reply	other threads:[~2025-02-14  5:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  6:58 [Intel-wired-lan] [iwl-next v9 0/9] ice: managing MSI-X in driver Michal Swiatkowski
2024-12-03  6:58 ` Michal Swiatkowski
2024-12-03  6:58 ` [Intel-wired-lan] [iwl-next v9 1/9] ice: count combined queues using Rx/Tx count Michal Swiatkowski
2024-12-03  6:58   ` Michal Swiatkowski
2024-12-03  6:58 ` [Intel-wired-lan] [iwl-next v9 2/9] ice: devlink PF MSI-X max and min parameter Michal Swiatkowski
2024-12-03  6:58   ` Michal Swiatkowski
2024-12-03  6:58 ` [Intel-wired-lan] [iwl-next v9 3/9] ice: remove splitting MSI-X between features Michal Swiatkowski
2024-12-03  6:58   ` Michal Swiatkowski
2024-12-03  6:58 ` [Intel-wired-lan] [iwl-next v9 4/9] ice: get rid of num_lan_msix field Michal Swiatkowski
2024-12-03  6:58   ` Michal Swiatkowski
2024-12-03  6:58 ` [Intel-wired-lan] [iwl-next v9 5/9] ice, irdma: move interrupts code to irdma Michal Swiatkowski
2024-12-03  6:58   ` Michal Swiatkowski
2025-02-13 19:20   ` [Intel-wired-lan] " Marcin Szycik
2025-02-14  5:41     ` Michal Swiatkowski [this message]
2024-12-03  6:58 ` [Intel-wired-lan] [iwl-next v9 6/9] ice: treat dyn_allowed only as suggestion Michal Swiatkowski
2024-12-03  6:58   ` Michal Swiatkowski
2024-12-03  6:58 ` [Intel-wired-lan] [iwl-next v9 7/9] ice: enable_rdma devlink param Michal Swiatkowski
2024-12-03  6:58   ` Michal Swiatkowski
2024-12-03  6:58 ` [Intel-wired-lan] [iwl-next v9 8/9] ice: simplify VF MSI-X managing Michal Swiatkowski
2024-12-03  6:58   ` Michal Swiatkowski
2024-12-03  6:58 ` [Intel-wired-lan] [iwl-next v9 9/9] ice: init flow director before RDMA Michal Swiatkowski
2024-12-03  6:58   ` Michal Swiatkowski

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=Z67XjwByeVSuLooq@mev-dev.igk.intel.com \
    --to=michal.swiatkowski@linux.intel.com \
    --cc=David.Laight@aculab.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=himasekharx.reddy.pucha@intel.com \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@resnulli.us \
    --cc=konrad.knitter@intel.com \
    --cc=marcin.szycik@intel.com \
    --cc=marcin.szycik@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=nex.sw.ncis.nat.hpm.dev@intel.com \
    --cc=pawel.chmielewski@intel.com \
    --cc=pio.raczynski@gmail.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=rafal.romanowski@intel.com \
    --cc=sridhar.samudrala@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.