All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linux-rt-users@vger.kernel.org
Subject: Possible bug in 23rt3 preempt-irqs-core.patch
Date: Thu, 25 Oct 2007 16:48:53 -0400	[thread overview]
Message-ID: <20071025204853.GB12268@windriver.com> (raw)

I was looking over the patches in preempt-irqs-core.patch in the broken
out 23rt3 series and came across this chunk:

-----------
@@ -325,6 +349,11 @@ int setup_irq(unsigned int irq, struct i
        if (!shared) {
                irq_chip_set_defaults(desc->chip);
 
+       /*
+        * Propagate any possible IRQF_NODELAY flag into IRQ_NODELAY:
+        */
+       recalculate_desc_flags(desc);
+
 #if defined(CONFIG_IRQ_PER_CPU)
                if (new->flags & IRQF_PERCPU)
                        desc->status |= IRQ_PER_CPU;
-----------

Note the recalculate is actually contained within the "if (!shared)"
even though at a casual glance the indentation suggests otherwise.

Looking at older versions of the broken out patches leads me to believe
the if clause should be after the recalculate.  I've attached a patch to
do just that, but if you'd rather I just respin the preempt-irqs-core.patch
then I could just as easily do that as well.

Thanks,
Paul.


--- linux-2.6.23-rt3/kernel/irq/manage.c~
+++ linux-2.6.23-rt3/kernel/irq/manage.c
@@ -354,14 +354,14 @@
 	if (new->flags & IRQF_NOBALANCING)
 		desc->status |= IRQ_NO_BALANCING;
 
-	if (!shared) {
-		irq_chip_set_defaults(desc->chip);
-
 	/*
 	 * Propagate any possible IRQF_NODELAY flag into IRQ_NODELAY:
 	 */
 	recalculate_desc_flags(desc);
 
+	if (!shared) {
+		irq_chip_set_defaults(desc->chip);
+
 #if defined(CONFIG_IRQ_PER_CPU)
 		if (new->flags & IRQF_PERCPU)
 			desc->status |= IRQ_PER_CPU;

             reply	other threads:[~2007-10-25 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 20:48 Paul Gortmaker [this message]
2007-10-26 13:22 ` Possible bug in 23rt3 preempt-irqs-core.patch Steven Rostedt
2007-10-26 15:38   ` Steven Rostedt

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=20071025204853.GB12268@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-rt-users@vger.kernel.org \
    /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.