25 Jan, 2008
1 commit
-
This adds kref_set() to the kref api for future use by people who really
know what they are doing with krefs...From: Evgeniy Polyakov
Cc: Kay Sievers
Signed-off-by: Greg Kroah-Hartman
28 Apr, 2007
1 commit
-
some atomic operations are only atomic, not ordered. Thus a CPU is allowed
to reorder memory references to an object to before the reference is
obtained. This fixes it.Signed-off-by: Oliver Neukum
Signed-off-by: Greg Kroah-Hartman
21 Dec, 2006
1 commit
-
With WARN_ON addition to kobject_init()
[ http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/dont-use/broken-out/gregkh-driver-kobject-warn.patch ]I started seeing following WARNING on CPU offline followed by online on my
x86_64 system.WARNING at lib/kobject.c:172 kobject_init()
Call Trace:
[] dump_trace+0xaa/0x3ef
[] show_trace+0x3a/0x50
[] dump_stack+0x15/0x17
[] kobject_init+0x3f/0x8a
[] kobject_register+0x1a/0x3e
[] sysdev_register+0x5b/0xf9
[] mce_create_device+0x77/0xf4
[] mce_cpu_callback+0x3a/0xe5
[] notifier_call_chain+0x26/0x3b
[] raw_notifier_call_chain+0x9/0xb
[] _cpu_up+0xb4/0xdc
[] cpu_up+0x2b/0x42
[] store_online+0x4a/0x72
[] sysdev_store+0x24/0x26
[] sysfs_write_file+0xcf/0xfc
[] vfs_write+0xae/0x154
[] sys_write+0x47/0x6f
[] system_call+0x7e/0x83
DWARF2 unwinder stuck at system_call+0x7e/0x83
Leftover inexact backtrace:This is a false positive as mce.c is unregistering/registering sysfs
interfaces cleanly on hotplug.kref_put() and conditional decrement of refcnt seems to be the root cause
for this and the patch below resolves the issue for me.Signed-off-by: Venkatesh Pallipadi
Signed-off-by: Andrew Morton
Signed-off-by: Greg Kroah-Hartman
21 Mar, 2006
1 commit
-
Avoid an atomic operation in kref_put() when the last reference is
dropped. On most platforms, atomic_read() is a plan read of the counter
and involves no atomic at all.Signed-off-by: Eric Dumazet
Signed-off-by: Greg Kroah-Hartman
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!