From: Holger Kiehl <Holger.Kiehl@dwd.de>
To: Alexey Dobriyan <adobriyan@sw.ru>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
dhaval@linux.vnet.ibm.com, vatsa@linux.vnet.ibm.com,
mingo@elte.hu, Greg KH <gregkh@suse.de>
Subject: Re: sysfs: duplicate filename '74' can not be created
Date: Fri, 7 Mar 2008 07:24:17 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0803070719260.22139@diagnostix.dwd.de> (raw)
In-Reply-To: <20080304160940.GC19059@localhost.sw.ru>
On Tue, 4 Mar 2008, Alexey Dobriyan wrote:
> [Cc'ing /sys/kernel/uids guys]
>
>> Mar 3 13:50:01 helena kernel: sysfs: duplicate filename '74' can not be created
>> Mar 3 13:50:01 helena kernel: WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
>> Mar 3 13:50:01 helena kernel: Pid: 21911, comm: sshd Not tainted 2.6.24.3 #1
>
> I see only one suspicious place: KOBJ_ADD is sent even if sysfs file
> creation failed and kobject is happily removed. But this almost
> certainly separate bug.
>
>
>
> You can try this debugging patch. Post several first consecutive messages.
> [crosses fingers]
>
Applied the patch and this time it oopsed immediatly. I just got one:
Mar 7 07:09:04 helena kernel: general protection fault: 0000 [1] SMP
Mar 7 07:09:04 helena kernel: CPU 3
Mar 7 07:09:04 helena kernel: Modules linked in: lm85 hwmon_vid i2c_amd756_s4882 bonding nf_conntrack_ftp nf_conntrack_netbios_ns ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables binfmt_misc video output ac floppy nvram ohci_hcd k8temp i2c_amd756 i2c_core button usbcore
Mar 7 07:09:04 helena kernel: Pid: 2983, comm: modprobe Not tainted 2.6.24.3-alexey #3
Mar 7 07:09:04 helena kernel: RIP: 0010:[<ffffffff8027931d>] [<ffffffff8027931d>] __kmalloc_node+0x95/0xc9
Mar 7 07:09:04 helena kernel: RSP: 0018:ffff81017d571de8 EFLAGS: 00010046
Mar 7 07:09:04 helena kernel: RAX: 0000000000000000 RBX: 00000000000080d0 RCX: ffffffff8026d2b1
Mar 7 07:09:04 helena kernel: RDX: ffff007265776f70 RSI: 00000000000080d0 RDI: ffffffff80554e38
Mar 7 07:09:04 helena kernel: RBP: ffff810200026800 R08: 00000000005184b0 R09: ffffffff80554e38
Mar 7 07:09:04 helena kernel: R10: 0000000000000000 R11: 0000000000000002 R12: 0000000000000286
Mar 7 07:09:04 helena kernel: R13: 00000000ffffffff R14: 00000000ffffffff R15: 00000000005184b0
Mar 7 07:09:04 helena kernel: FS: 00002b66d114c6f0(0000) GS:ffff81027e30e300(0000) knlGS:0000000000000000
Mar 7 07:09:04 helena kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Mar 7 07:09:04 helena kernel: CR2: 0000003254acc030 CR3: 000000017d530000 CR4: 00000000000006e0
Mar 7 07:09:04 helena kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 7 07:09:04 helena kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Mar 7 07:09:04 helena kernel: Process modprobe (pid: 2983, threadinfo ffff81017d570000, task ffff81017df3d5c0)
Mar 7 07:09:04 helena kernel: Stack: ffff81027d2fb740 ffffc200017e39a8 ffff81027d2fba00 00000000000000d0
Mar 7 07:09:04 helena kernel: ffffc200017e33e8 ffffffff8026d2b1 0000000000000163 ffffc200017e39a8
Mar 7 07:09:04 helena kernel: 0000000000000018 ffffc200017e39a8 0000000000000018 ffffc200017e2f80
Mar 7 07:09:04 helena kernel: Call Trace:
Mar 7 07:09:04 helena kernel: [<ffffffff8026d2b1>] __vmalloc_area_node+0x71/0x185
Mar 7 07:09:04 helena kernel: [<ffffffff80248ec0>] sys_init_module+0x94d/0x1872
Mar 7 07:09:04 helena kernel: [<ffffffff8020b61e>] system_call+0x7e/0x83
Mar 7 07:09:04 helena kernel:
Mar 7 07:09:04 helena kernel:
Mar 7 07:09:04 helena kernel: Code: 48 8b 04 c2 48 89 45 00 41 54 9d 31 c0 c1 eb 0f 48 85 d2 0f
Mar 7 07:09:04 helena kernel: RIP [<ffffffff8027931d>] __kmalloc_node+0x95/0xc9
Mar 7 07:09:04 helena kernel: RSP <ffff81017d571de8>
Mar 7 07:09:04 helena kernel: ---[ end trace 82b7eaeeb11c3ab5 ]---
After this the system was no longer reachable. Note, as before it always
happens on CPU3.
Holger
next prev parent reply other threads:[~2008-03-07 7:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 16:09 Alexey Dobriyan
2008-03-04 16:33 ` Dhaval Giani
2008-03-04 19:24 ` Greg KH
2008-03-05 8:59 ` Dhaval Giani
2008-03-06 6:00 ` Greg KH
2008-03-06 9:15 ` Alexey Dobriyan
2008-03-07 7:32 ` Holger Kiehl
2008-03-07 7:24 ` Holger Kiehl [this message]
2008-03-07 7:56 ` Holger Kiehl
2008-03-13 7:33 ` Holger Kiehl
-- strict thread matches above, loose matches on Subject: below --
2008-03-03 14:58 Holger Kiehl
2008-03-03 15:50 ` Alexey Dobriyan
2008-03-03 16:05 ` Holger Kiehl
2008-03-03 16:14 ` Holger Kiehl
2008-03-03 16:17 ` Alexey Dobriyan
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=Pine.LNX.4.64.0803070719260.22139@diagnostix.dwd.de \
--to=holger.kiehl@dwd.de \
--cc=adobriyan@sw.ru \
--cc=dhaval@linux.vnet.ibm.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.com \
/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®