From: Florian Westphal <fw@strlen.de>
To: Adam Nielsen <a.nielsen@shikadi.net>
Cc: Patrick McHardy <kaber@trash.net>,
Jan Engelhardt <jengelh@medozas.de>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH v3] Add refcounts to LED target
Date: Thu, 8 Apr 2010 23:07:22 +0200 [thread overview]
Message-ID: <20100408210722.GA18974@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <4BBD478F.4050208@shikadi.net>
Adam Nielsen <a.nielsen@shikadi.net> wrote:
> +static struct xt_led_info_internal *led_trigger_lookup(const char *name)
> +{
> + struct xt_led_info_internal *ledinternal;
> +
> + list_for_each_entry(ledinternal, &xt_led_triggers, list) {
> + if (!strcmp(name, ledinternal->netfilter_led_trigger.name)) {
> + mutex_unlock(&xt_led_mutex);
This mutex_unlock looks out of place...
> static int led_tg_check(const struct xt_tgchk_param *par)
> {
> struct xt_led_info *ledinfo = par->targinfo;
> @@ -91,11 +109,26 @@ static int led_tg_check(const struct xt_tgchk_param *par)
> return -EINVAL;
> }
>
> + mutex_lock(&xt_led_mutex);
> +
> + ledinternal = led_trigger_lookup(ledinfo->id);
> + if (ledinternal) {
> + ledinternal->refcnt++;
> + goto out;
...its unlocked again here via goto.
> + err = -ENOMEM;
> ledinternal = kzalloc(sizeof(struct xt_led_info_internal), GFP_KERNEL);
> if (!ledinternal)
> - return -ENOMEM;
> + goto exit_mutex_only;
> +
> + ledinternal->trigger_id = kzalloc(strlen(ledinfo->id) + 1, GFP_KERNEL);
kstrdup()?
next prev parent reply other threads:[~2010-04-08 21:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 1:46 Avoiding multiple calls to xt_target.checkentry Adam Nielsen
2009-05-24 7:34 ` Jan Engelhardt
2009-05-27 23:07 ` Adam Nielsen
2009-05-28 21:06 ` Jan Engelhardt
2009-06-03 9:25 ` Patrick McHardy
2009-06-03 11:03 ` Adam Nielsen
2009-11-05 15:00 ` Patrick McHardy
2009-11-05 18:40 ` Jan Engelhardt
2009-11-05 18:43 ` Patrick McHardy
2009-11-05 22:04 ` Adam Nielsen
2009-11-06 14:56 ` Patrick McHardy
2009-11-29 1:43 ` [PATCH] Add refcounts to LED target Adam Nielsen
2009-11-29 10:12 ` Jan Engelhardt
2009-11-29 11:33 ` Adam Nielsen
2009-11-29 15:49 ` Jan Engelhardt
2009-12-01 10:05 ` Patrick McHardy
2009-12-06 10:09 ` Adam Nielsen
2009-12-06 13:24 ` Patrick McHardy
2010-03-25 14:01 ` Patrick McHardy
2010-03-25 14:05 ` Jan Engelhardt
2010-03-25 14:08 ` Patrick McHardy
2010-03-27 4:05 ` Adam Nielsen
2010-03-27 11:15 ` Jan Engelhardt
2010-03-27 11:39 ` Adam Nielsen
2010-03-27 11:55 ` Jan Engelhardt
2010-03-28 1:25 ` [PATCH v2] " Adam Nielsen
2010-04-04 11:30 ` Jan Engelhardt
2010-04-07 16:15 ` Patrick McHardy
2010-04-08 3:03 ` [PATCH v3] " Adam Nielsen
2010-04-08 11:33 ` Patrick McHardy
2010-04-08 12:45 ` Jan Engelhardt
2010-04-08 12:57 ` Patrick McHardy
2010-04-08 23:06 ` [PATCH v4] " Adam Nielsen
2010-04-09 14:52 ` Patrick McHardy
2010-04-08 21:07 ` Florian Westphal [this message]
2010-04-08 22:45 ` [PATCH v3] " Adam Nielsen
2010-03-27 18:42 ` [PATCH] " Jan Engelhardt
2010-03-28 1:58 ` Adam Nielsen
2010-04-04 11:59 ` Jan Engelhardt
2010-04-08 3:15 ` input-layer LEDs as LED-class devices (was: Add refcounts to LED target) Adam Nielsen
2010-04-08 8:03 ` Jan Engelhardt
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=20100408210722.GA18974@Chamillionaire.breakpoint.cc \
--to=fw@strlen.de \
--cc=a.nielsen@shikadi.net \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@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 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).