From: Thomas Gleixner <tglx@linutronix.de>
To: Milton Miller <miltonm@bga.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] irq: radix_tree_insert can fail
Date: Wed, 25 May 2011 10:18:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1105251017460.3078@ionos> (raw)
In-Reply-To: <radix-insert-can-fail@mdm.bga.com>
On Wed, 25 May 2011, Milton Miller wrote:
> Check the insert, and if it fails cleanup and free all partial work.
>
> Sparse irq was not checking the return code from radix_tree_insert,
> but it may need to allocate memory and can fail. If it failed,
> it still claimed success to the caller but the affected irq(s) are
> unavailable and the reference to the affected descriptors is leaked.
>
> Signed-off-by: Milton Miller <miltonm@bga.com>
> ---
> I started by tring to change free_desc to take the descriptor pointer
> and pushing that down, but that soon ran into conflicts between the
> array and sparse implementations, and/or the old dynamic irq cleanup
> function that is still used by some architectures. This version is
> targeted, and also protects against scribbles to irq_data.irq.
The simpler solution is to move irq_insert_desc() into alloc_desc()
and deal with the error case there.
Thanks,
tglx
next prev parent reply other threads:[~2011-05-25 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <generic-irq-changes@mdm.bga.com>
2011-05-25 6:34 ` Milton Miller
2011-05-25 8:18 ` Thomas Gleixner [this message]
2011-05-25 10:48 ` Milton Miller
2011-05-25 6:34 ` [PATCH RFC 4/4] irq: allow a per-allocation upper limit when allocating irqs Milton Miller
2011-05-25 7:55 ` Ingo Molnar
2011-05-25 8:32 ` Thomas Gleixner
2011-05-27 3:38 ` Grant Likely
2011-05-25 6:34 ` [PATCH 1/4] sparse irq: protect irq_to_desc against irq_free_descs Milton Miller
2011-05-25 8:14 ` Thomas Gleixner
2011-05-25 10:49 ` Milton Miller
2011-05-25 10:54 ` Thomas Gleixner
2011-05-25 6:34 ` [PATCH 3/4] irq: remove unnecessary __ref on irq_alloc_descs Milton Miller
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.1105251017460.3078@ionos \
--to=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®