From: Andrew Morton <akpm@osdl.org>
To: Abhay Salunke <Abhay_Salunke@dell.com>
Cc: linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
abhay_salunke@dell.com, matt_domsch@dell.com, greg@kroah.com
Subject: Re: [patch 2.6.12-rc3] dell_rbu: Resubmitting patch for new Dell BIOS update driver
Date: Sun, 19 Jun 2005 17:36:36 -0700 [thread overview]
Message-ID: <20050619173636.50acad6f.akpm@osdl.org> (raw)
In-Reply-To: <20050615175946.GA1495@littleblue.us.dell.com>
This patch causes my x86_64 box to oops during udev startup:
Starting udev: Unable to handle kernel NULL pointer dereference at 0000000000000040 RIP:
<ffffffff801a807c>{sysfs_readdir+350}
PGD 17be07067 PUD 17add5067 PMD 0
Oops: 0000 [1] PREEMPT SMP
CPU 2
Modules linked in:
Pid: 27686, comm: udevstart Not tainted 2.6.12-mm1
RIP: 0010:[<ffffffff801a807c>] <ffffffff801a807c>{sysfs_readdir+350}
RSP: 0018:ffff81017adc5ea8 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff81017ceb18d0 RCX: 0000000000000007
RDX: ffffffff80184516 RSI: ffff81017adc5f38 RDI: ffff81017b45d41c
RBP: ffff81017aa5cd50 R08: 0000000000015bc0 R09: 000000302062d6b8
R10: 000000302062d6b8 R11: 0000000000000246 R12: ffff81017ceb18c8
R13: ffff81017fc663a0 R14: ffff81017edfaa70 R15: ffff81017b45d414
FS: 00002aaaaaadcde0(0000) GS:ffffffff805a0780(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000040 CR3: 000000017f2d5000 CR4: 00000000000006e0
Process udevstart (pid: 27686, threadinfo ffff81017adc4000, task ffff81017cb77030)
Stack: 0000000700000246 ffffffff80184516 ffff81017adc5f38 ffff81017edfaa70
ffff81017fc67860 00000000fffffffe ffff81017fc67928 ffffffff80184516
ffff81017adc5f38 ffffffff8018427a
Call Trace:<ffffffff80184516>{filldir64+0} <ffffffff80184516>{filldir64+0}
<ffffffff8018427a>{vfs_readdir+126} <ffffffff80184643>{sys_getdents64+116}
<ffffffff80171969>{sys_close+132} <ffffffff8010d9e2>{system_call+126}
Code: 48 8b 40 40 eb 11 48 8b 3d 4f eb 3d 00 be 02 00 00 00 e8 86
next prev parent reply other threads:[~2005-06-20 0:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 17:59 Abhay Salunke
2005-06-16 18:52 ` Greg KH
2005-06-20 0:36 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-20 23:50 [patch 2.6.12-rc3]dell_rbu: " Abhay Salunke
2005-07-09 1:07 Abhay Salunke
2005-06-17 14:55 [patch 2.6.12-rc3] dell_rbu: " Abhay_Salunke
2005-06-17 15:29 ` Greg KH
2005-06-02 23:26 Abhay Salunke
2005-06-02 23:58 ` Marcel Holtmann
2005-06-03 12:32 ` Andreas Henriksson
2005-06-05 21:51 ` Jesper Juhl
2005-06-02 18:36 Abhay Salunke
2005-06-02 21:44 ` Marcel Holtmann
2005-05-26 18:43 Abhay_Salunke
2005-05-26 16:37 Abhay_Salunke
2005-05-26 16:56 ` Matt Domsch
2005-05-26 20:37 ` Greg KH
2005-05-26 21:36 ` Marcel Holtmann
2005-05-23 14:52 Abhay_Salunke
2005-05-23 14:58 ` Arjan van de Ven
2005-05-23 14:59 ` Marcel Holtmann
2005-05-23 15:48 ` Greg KH
2005-05-19 12:03 Abhay_Salunke
2005-05-19 14:42 ` Greg KH
2005-05-18 18:13 Abhay Salunke
2005-05-19 3:32 ` Greg KH
2005-05-13 19:00 Abhay Salunke
2005-05-13 21:11 ` 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=20050619173636.50acad6f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Abhay_Salunke@dell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt_domsch@dell.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®