mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erhard Furtner <erhard_f@mailbox.org>
To: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Cc: ville.syrjala@linux.intel.com, o-takashi@sakamocchi.jp
Subject: Re: BUG: spinlock bad magic on CPU#1, irq/39-firewire/245 (v6.18-rc4, ppc64)
Date: Sat, 15 Nov 2025 00:54:52 +0100	[thread overview]
Message-ID: <f197fe16-1ef2-4d00-93a4-1db68deade37@mailbox.org> (raw)
In-Reply-To: <20251111150030.GA210402@workstation.local>

On 11/14/25 15:27, Takashi Sakamoto wrote:
 > Hi,
 >
 > Thanks for your sending the patch. I completely overlooked the lack of
 > initialization... Your patch fixes the same issue reported by Erhard
 > Furtner[1].
 >
 > On Fri, Nov 14, 2025 at 12:25:31AM +0200, Ville Syrjala wrote:
 >> Cc: linux1394-devel@lists.sourceforge.net
 >> Cc: Takashi Sakamoto <o-takashi@sakamocchi.jp>
 >> Fixes: 7d138cb269db ("firewire: core: use spin lock specific to 
topology map")
 >> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
 >> ---
 >>   drivers/firewire/core-card.c | 2 ++
 >>   1 file changed, 2 insertions(+)
 >
 > Applied to for-linus branch. I will send it to upstream as a part of
 > fixes for v6.18-rc6 kernel.
 >
 > [1] 
https://lore.kernel.org/lkml/992eaf94-6fbb-4611-9a29-2db2e2148965@mailbox.org/

I can confirm the patch from 
https://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git/commit/?h=for-linus&id=2ea68aed6b0d327c78755c954827f25452e42f3f 
applies on v6.18-rc5 and fixes my problem.

Thanks!

Regards,
Erhard

      reply	other threads:[~2025-11-14 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-09 14:17 Erhard Furtner
2025-11-11 12:41 ` Erhard Furtner
2025-11-11 15:00   ` Takashi Sakamoto
2025-11-14 23:54     ` Erhard Furtner [this message]

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=f197fe16-1ef2-4d00-93a4-1db68deade37@mailbox.org \
    --to=erhard_f@mailbox.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=o-takashi@sakamocchi.jp \
    --cc=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®