Re: [patch] module: potential deadlock in error path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [patch] module: potential deadlock in error path
From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Date: Mon, 21 Jan 2013 11:58:36 +0300
Cc: Rusty Russell <rusty@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, kernel-janitors <kernel-janitors@xxxxxxxxxxxxxxx>, Alexander Graf <agraf@xxxxxxx>, Prarit Bhargava <prarit@xxxxxxxxxx>, Sasha Levin <sasha.levin@xxxxxxxxxx>
In-reply-to: <CA+55aFyhfuLJqsEiAJ3jyf_OikgZroFkfBW1i-LYwCr0YOVX1w@mail.gmail.com>
User-agent: Mutt/1.5.21 (2010-09-15)

Rusty, you have this right?  I like Linus's version.  Could you give
me a Reported-by tag?

regards,
dan carpenter

--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

References:
- [patch] module: potential deadlock in error path
  - From: Dan Carpenter
- Re: [patch] module: potential deadlock in error path
  - From: Rusty Russell
- Re: [patch] module: potential deadlock in error path
  - From: Linus Torvalds
- Re: [patch] module: potential deadlock in error path
  - From: Rusty Russell
- Re: [patch] module: potential deadlock in error path
  - From: Linus Torvalds

Prev by Date: Re: [patch] f2fs: use _safe() version of list_for_each
Next by Date: Re: [patch] f2fs: use _safe() version of list_for_each
Previous by thread: Re: [patch] module: potential deadlock in error path
Next by thread: [patch] enic: change sprintf() to snprintf()
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Development] [Kernel Announce] [Kernel Newbies] [Linux Networking Development] [Share Photos] [IDE] [Security] [Git] [Netfilter] [Yosemite News] [MIPS Linux] [ARM Linux] [Device Mapper]

Powered by Linux