From: "Ken Chen" <kenchen@google.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Kay Sievers" <kay.sievers@vrfy.org>,
"Alexey Dobriyan" <adobriyan@sw.ru>
Subject: Re: 2.6.21-git11: BUG in loop.ko
Date: Thu, 10 May 2007 23:10:28 -0700 [thread overview]
Message-ID: <b040c32a0705102310m5ec647an2b3aa9f74e2ed450@mail.gmail.com> (raw)
In-Reply-To: <20070509170521.ec2c9ae7.akpm@linux-foundation.org>
On 5/9/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 09 May 2007 16:52:41 -0700
> Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
> > Seems to be getting a 0 refcount. I don't see anything in the recent
> > changes which might cause this, but this is relatively new behaviour.
> > It was working for me in the 2.6.21-pre time period, but I haven't tried
> > this since 2.6.21 was released.
> >
> > The BUG is actually triggered by the __module_get(THIS_MODULE) in
> > loop_set_fd.
>
> A few people have been playing with module refcounting lately. Did you
> work out a reproduce-it recipe?
Ah, it's a mis-understanding on what kobj_probe_t function is suppose
to return on success. When we open loop device that has not been
initialized, we probe it via:
do_open
get_gendisk
kobj_lookup
loop_probe
Notice that in kobj_lookup(), when p->probe() returns non-zero value
(I presume it is an -ERRNO), it breaks out of the loop and propagate
the return value, otherwise, loops back to the beginning of the for
loop and retry, and in there get_disk() will be called via p->lock()
to get a ref against the module.
kobj_look_up(...) {
retry:
mutex_lock(domain->lock);
for (p = domain->probes[MAJOR(dev) % 255]; p; p = p->next) {
...
if (kobj)
return kobj;
goto retry;
}
So loop_probe() mistakenly returned wrong status and leads to future
oops on inconsistent module ref count. The following patch fixes the
issue.
Signed-off-by: Ken Chen <kenchen@google.com>
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 18cdd8c..40f7bc2 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -1460,6 +1460,7 @@ static void loop_del_one(struct loop_device *lo)
kfree(lo);
}
+/* return NULL for success, or return non-zero value if there are error */
static struct kobject *loop_probe(dev_t dev, int *part, void *data)
{
unsigned int number = dev & MINORMASK;
@@ -1474,8 +1475,8 @@ static struct kobject *loop_probe
*part = 0;
if (IS_ERR(lo))
return (void *)lo;
- else
- return &lo->lo_disk->kobj;
+
+ return NULL;
}
static int __init loop_init(void)
next prev parent reply other threads:[~2007-05-11 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 23:52 Jeremy Fitzhardinge
2007-05-10 0:05 ` Andrew Morton
2007-05-10 0:20 ` Jeremy Fitzhardinge
2007-05-10 7:39 ` Alexey Dobriyan
2007-05-10 10:33 ` Alexey Dobriyan
2007-05-11 6:10 ` Ken Chen [this message]
2007-05-11 15:09 ` Jeremy Fitzhardinge
2007-05-11 7:40 devzero
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=b040c32a0705102310m5ec647an2b3aa9f74e2ed450@mail.gmail.com \
--to=kenchen@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=adobriyan@sw.ru \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®