All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: "Nechita, Ionut" <ionut.nechita@intel.com>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: WARN Kernel v6.9-evl-rebase - do_int80_emulation
Date: Wed, 22 May 2024 15:18:51 +0200	[thread overview]
Message-ID: <87a5kirnjs.fsf@xenomai.org> (raw)
In-Reply-To: <PH0PR11MB59496A3A9FFCB39B7715813AF4E92@PH0PR11MB5949.namprd11.prod.outlook.com>


"Nechita, Ionut" <ionut.nechita@intel.com> writes:

> Hi Philippe,
>
> You are reproduce this issue without CONFIG_EVL and CONFIG_DOVETAIL enabled in config kernel?
>
> CONFIG_EVL=n
> CONFIG_DOVETAIL=n

Yep, this should fix the issue. This bug might have been there since the
introduction of scoped guards for hard spinlocks. Checking and
backporting fixes if so.

commit b51c3afd66c8763bed7a4b8258cc5cf5c8ebd719 (HEAD -> rebase/v6.9-evl)
Author: Philippe Gerum <rpm@xenomai.org>
Date:   Wed May 22 15:16:52 2024 +0200

    irq_pipeline: provide placeholder for scoped guard w/o IRQ_PIPELINE
    
    Signed-off-by: Philippe Gerum <rpm@xenomai.org>

diff --git a/include/linux/spinlock.h b/include/linux/spinlock.h
index eb8b4d386e942..545368b045e52 100644
--- a/include/linux/spinlock.h
+++ b/include/linux/spinlock.h
@@ -612,7 +612,24 @@ DEFINE_LOCK_GUARD_1(hard_spinlock_irqsave, hard_spinlock_t,
 		    hard_spin_unlock_irqrestore((raw_spinlock_t *)_T->lock,
 						_T->flags),
 		    unsigned long flags)
-#endif
+#else  /* !CONFIG_IRQ_PIPELINE */
+DEFINE_LOCK_GUARD_1(hard_spinlock, raw_spinlock_t,
+		    raw_spin_lock(_T->lock),
+		    raw_spin_unlock(_T->lock))
+
+DEFINE_LOCK_GUARD_1(hard_spinlock_nested, raw_spinlock_t,
+		    raw_spin_lock_nested(_T->lock, SINGLE_DEPTH_NESTING),
+		    raw_spin_unlock(_T->lock))
+
+DEFINE_LOCK_GUARD_1(hard_spinlock_irq, raw_spinlock_t,
+		    raw_spin_lock_irq(_T->lock),
+		    raw_spin_unlock_irq(_T->lock))
+
+DEFINE_LOCK_GUARD_1(hard_spinlock_irqsave, raw_spinlock_t,
+		    raw_spin_lock_irqsave(_T->lock, _T->flags),
+		    raw_spin_unlock_irqrestore(_T->lock, _T->flags),
+		    unsigned long flags)
+#endif  /* !CONFIG_IRQ_PIPELINE */
 
 DEFINE_LOCK_GUARD_1(spinlock, spinlock_t,
 		    spin_lock(_T->lock),

-- 
Philippe.

  reply	other threads:[~2024-05-22 13:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 11:49 WARN Kernel v6.9-evl-rebase - do_int80_emulation Nechita, Ionut
2024-05-17 12:12 ` Philippe Gerum
2024-05-17 12:40   ` Nechita, Ionut
2024-05-17 13:15     ` Philippe Gerum
2024-05-17 13:23       ` Nechita, Ionut
2024-05-17 13:38         ` Nechita, Ionut
2024-05-20  9:49           ` Nechita, Ionut
2024-05-22 13:18             ` Philippe Gerum [this message]
2024-05-22 13:23               ` Nechita, Ionut
2024-05-22 15:26                 ` Nechita, Ionut

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=87a5kirnjs.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=ionut.nechita@intel.com \
    --cc=xenomai@lists.linux.dev \
    /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.