From: Simon Horman <horms@kernel.org>
To: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
netdev@vger.kernel.org,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v1] ixgbe: initialize aci.lock before it's used
Date: Mon, 16 Jun 2025 20:12:41 +0100 [thread overview]
Message-ID: <20250616191241.GA5000@horms.kernel.org> (raw)
In-Reply-To: <20250616133636.1304288-1-jedrzej.jagielski@intel.com>
On Mon, Jun 16, 2025 at 03:36:36PM +0200, Jedrzej Jagielski wrote:
> Currently aci.lock is initialized too late. A bunch of ACI callbacks
> using the lock are called prior it's initialized.
>
> Commit 337369f8ce9e ("locking/mutex: Add MUTEX_WARN_ON() into fast path")
> highlights that issue what results in call trace.
>
> [ 4.092899] DEBUG_LOCKS_WARN_ON(lock->magic != lock)
> [ 4.092910] WARNING: CPU: 0 PID: 578 at kernel/locking/mutex.c:154 mutex_lock+0x6d/0x80
> [ 4.098757] Call Trace:
> [ 4.098847] <TASK>
> [ 4.098922] ixgbe_aci_send_cmd+0x8c/0x1e0 [ixgbe]
> [ 4.099108] ? hrtimer_try_to_cancel+0x18/0x110
> [ 4.099277] ixgbe_aci_get_fw_ver+0x52/0xa0 [ixgbe]
> [ 4.099460] ixgbe_check_fw_error+0x1fc/0x2f0 [ixgbe]
> [ 4.099650] ? usleep_range_state+0x69/0xd0
> [ 4.099811] ? usleep_range_state+0x8c/0xd0
> [ 4.099964] ixgbe_probe+0x3b0/0x12d0 [ixgbe]
> [ 4.100132] local_pci_probe+0x43/0xa0
> [ 4.100267] work_for_cpu_fn+0x13/0x20
> [ 4.101647] </TASK>
>
> Move aci.lock mutex initialization to ixgbe_sw_init() before any ACI
> command is sent. Along with that move also related SWFW semaphore in
> order to reduce size of ixgbe_probe() and that way all locks are
> initialized in ixgbe_sw_init().
>
> Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Fixes: 4600cdf9f5ac ("ixgbe: Enable link management in E610 device")
> Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
netdev@vger.kernel.org,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [PATCH iwl-net v1] ixgbe: initialize aci.lock before it's used
Date: Mon, 16 Jun 2025 20:12:41 +0100 [thread overview]
Message-ID: <20250616191241.GA5000@horms.kernel.org> (raw)
In-Reply-To: <20250616133636.1304288-1-jedrzej.jagielski@intel.com>
On Mon, Jun 16, 2025 at 03:36:36PM +0200, Jedrzej Jagielski wrote:
> Currently aci.lock is initialized too late. A bunch of ACI callbacks
> using the lock are called prior it's initialized.
>
> Commit 337369f8ce9e ("locking/mutex: Add MUTEX_WARN_ON() into fast path")
> highlights that issue what results in call trace.
>
> [ 4.092899] DEBUG_LOCKS_WARN_ON(lock->magic != lock)
> [ 4.092910] WARNING: CPU: 0 PID: 578 at kernel/locking/mutex.c:154 mutex_lock+0x6d/0x80
> [ 4.098757] Call Trace:
> [ 4.098847] <TASK>
> [ 4.098922] ixgbe_aci_send_cmd+0x8c/0x1e0 [ixgbe]
> [ 4.099108] ? hrtimer_try_to_cancel+0x18/0x110
> [ 4.099277] ixgbe_aci_get_fw_ver+0x52/0xa0 [ixgbe]
> [ 4.099460] ixgbe_check_fw_error+0x1fc/0x2f0 [ixgbe]
> [ 4.099650] ? usleep_range_state+0x69/0xd0
> [ 4.099811] ? usleep_range_state+0x8c/0xd0
> [ 4.099964] ixgbe_probe+0x3b0/0x12d0 [ixgbe]
> [ 4.100132] local_pci_probe+0x43/0xa0
> [ 4.100267] work_for_cpu_fn+0x13/0x20
> [ 4.101647] </TASK>
>
> Move aci.lock mutex initialization to ixgbe_sw_init() before any ACI
> command is sent. Along with that move also related SWFW semaphore in
> order to reduce size of ixgbe_probe() and that way all locks are
> initialized in ixgbe_sw_init().
>
> Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Fixes: 4600cdf9f5ac ("ixgbe: Enable link management in E610 device")
> Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-06-16 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 13:36 [Intel-wired-lan] [PATCH iwl-net v1] ixgbe: initialize aci.lock before it's used Jedrzej Jagielski
2025-06-16 13:36 ` Jedrzej Jagielski
2025-06-16 19:12 ` Simon Horman [this message]
2025-06-16 19:12 ` Simon Horman
2025-06-17 5:39 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-06-17 5:39 ` Loktionov, Aleksandr
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=20250616191241.GA5000@horms.kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--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.