From: Thomas Gleixner <tglx@linutronix.de>
To: Milton Miller <miltonm@bga.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org
Subject: Re: genirq: Ensure we locate the passed IRQ in irq_alloc_descs()
Date: Fri, 3 Jun 2011 18:25:01 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1106031823310.3078@ionos> (raw)
In-Reply-To: <locate-from-more@mdm.bga.com>
On Fri, 3 Jun 2011, Milton Miller wrote:
> On Fri, 3 Jun 2011 about 11:42:17 +0100, Mark Brown wrote:
> > On Fri, Jun 03, 2011 at 04:24:02AM -0500, Milton Miller wrote:
> > > On Thu, 02 Jun 2011 17:55:13 -0000, Mark Brown wrote:
> >
> > > > start = bitmap_find_next_zero_area(allocated_irqs, IRQ_BITMAP_BITS,
> >
> > > and then right after this the code continues:
> >
> > > ret = -EEXIST;
> > > if (irq >=0 && start != irq)
> > > goto err;
> >
> > > This patch enables exactly the calls I want to forbid ! Why do
> >
> > Which you wish to forbid because...? You've not articulated any
> > motivation for doing this which makes it rather hard to engage here.
>
> In 2.6.39 all calls to irq_alloc_descs were from the helpers. Either
> from irq_alloc_descriptor_at , which says "I need this exact irq",
> or from irq_alloc_desc, which says "give me any irq".
That does not prevent a caller with uses irq_alloc_descs() directly
with the wrong arguments. So we want to sanity check this.
Thanks,
tglx
next prev parent reply other threads:[~2011-06-03 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 17:55 [PATCH] genirq: Ensure we locate the passed IRQ in irq_alloc_descs() Mark Brown
2011-06-03 9:24 ` Milton Miller
2011-06-03 10:42 ` Mark Brown
2011-06-03 14:43 ` Milton Miller
2011-06-03 15:06 ` Mark Brown
2011-06-03 16:25 ` Thomas Gleixner [this message]
2011-06-04 0:23 ` Milton Miller
2011-06-04 9:51 ` Mark Brown
2011-06-06 19:42 ` Grant Likely
2011-06-06 20:57 ` Mark Brown
2011-06-06 21:33 ` Grant Likely
2011-06-03 12:59 ` [tip:irq/urgent] " tip-bot for Mark Brown
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=alpine.LFD.2.02.1106031823310.3078@ionos \
--to=tglx@linutronix.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miltonm@bga.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;
as well as URLs for NNTP newsgroup(s).