From: Greg KH <greg@kroah.com>
To: Tejun Heo <tj@kernel.org>
Cc: Colin Guthrie <cguthrie@mandriva.org>,
Kay Sievers <kay.sievers@vrfy.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: get_device_parent() race bug
Date: Mon, 5 Oct 2009 16:39:19 -0700 [thread overview]
Message-ID: <20091005233919.GA13029@kroah.com> (raw)
In-Reply-To: <4ABC7DB5.9010402@kernel.org>
On Fri, Sep 25, 2009 at 05:22:13PM +0900, Tejun Heo wrote:
> Hello, Greg, Kay, Guthrie.
>
> This problem was reported in bko#14023. (aiee.. again, sorry about
> the delay)
>
> http://bugzilla.kernel.org/show_bug.cgi?id=14023
>
> sysfs is creating several devices in cuse class concurrently and with
> CONFIG_SYSFS_DEPRECATED turned off, it triggers the following oops.
>
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000038
> IP: [<ffffffff81158b0a>] sysfs_addrm_start+0x4a/0xf0
> PGD 75bb067 PUD 75be067 PMD 0
> Oops: 0000 [#1] PREEMPT SMP
> last sysfs file: /sys/devices/system/cpu/cpu7/topology/core_siblings
> CPU 1
> Modules linked in: cuse fuse
> Pid: 4737, comm: osspd Not tainted 2.6.31-work #77
> RIP: 0010:[<ffffffff81158b0a>] [<ffffffff81158b0a>] sysfs_addrm_start+0x4a/0xf0
> RSP: 0018:ffff88000042f8f8 EFLAGS: 00010296
> RAX: ffff88000042ffd8 RBX: 0000000000000000 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: ffff880007eef660 RDI: 0000000000000001
> RBP: ffff88000042f918 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000001 R11: ffffffff81158b0a R12: ffff88000042f928
> R13: 00000000fffffff4 R14: 0000000000000000 R15: ffff88000042f9a0
> FS: 00007fe93905a950(0000) GS:ffff880008600000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000000038 CR3: 00000000077c9000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process osspd (pid: 4737, threadinfo ffff88000042e000, task ffff880007eef040)
> Stack:
> ffff880005da10e8 0000000011cc8d6e ffff88000042f928 ffff880003d28a28
> <0> ffff88000042f988 ffffffff811592d7 0000000000000000 0000000000000000
> <0> 0000000000000000 0000000000000000 ffff88000042f958 0000000011cc8d6e
> Call Trace:
> [<ffffffff811592d7>] create_dir+0x67/0xe0
> [<ffffffff811593a8>] sysfs_create_dir+0x58/0xb0
> [<ffffffff8128ca7c>] ? kobject_add_internal+0xcc/0x220
> [<ffffffff812942e1>] ? vsnprintf+0x3c1/0xb90
> [<ffffffff8128cab7>] kobject_add_internal+0x107/0x220
> [<ffffffff8128cd37>] kobject_add_varg+0x47/0x80
> [<ffffffff8128ce53>] kobject_add+0x53/0x90
> [<ffffffff81357d84>] device_add+0xd4/0x690
> [<ffffffff81356c2b>] ? dev_set_name+0x4b/0x70
> [<ffffffffa001a884>] cuse_process_init_reply+0x2b4/0x420 [cuse]
> ...
>
> The problem is that kobject_add_internal() first adds a kobject to the
> kset and then try to create sysfs directory for it. If the creation
> fails,
Why would the creation fail? How are you triggering this?
> it remove the kobject from the kset. get_device_parent()
> accesses class_dirs kset while only holding class_dirs.list_lock to
> see whether the cuse class dir exists. But when it exists, it may not
> have finished initialization yet or may fail and get removed soon. In
> the above case, the former happened so the second one ends up trying
> to create subdirectory under null sysfs_dirent.
What kobjects are you using here? Shouldn't you be using a 'struct
device' instead?
> Patch attached at the end of this email solves this problem in an ugly
> way.
>
> <rant>
> One of the things I really dislike about these k* stuff is that the
> API advertises much more than they're actually capable of. The
> encapsulated synchronization might look like a good idea but it fails
> horribly in practice because these things are always used in
> connection with other objects. The API just tricks developers to
> think that all the complexities have been handled and nicely
> encapsulated when the reality is those are just hidden under giant
> pile of abstract crap. I really hope someday driver model can do away
> with all these k* stuff and use just necessary amount of abstraction
> like other sane kernel subsystems. :-(
> </rant>
I agree, if this happens, it is a failure of the driver model code.
But I don't see what the patch is solving here, how is this triggered?
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-05 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 8:22 get_device_parent() race bug Tejun Heo
2009-10-04 0:35 ` Tejun Heo
2009-10-05 14:22 ` Greg KH
2009-10-06 1:15 ` Tejun Heo
2009-10-06 3:05 ` Greg KH
2009-10-06 3:29 ` Kay Sievers
2009-10-05 23:39 ` Greg KH [this message]
2009-10-06 1:35 ` Tejun Heo
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=20091005233919.GA13029@kroah.com \
--to=greg@kroah.com \
--cc=cguthrie@mandriva.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.