From: Olaf Hering <olh@suse.de>
To: linux-kernel@vger.kernel.org
Subject: scsi proc_info called unconditionally
Date: Sat, 16 Aug 2003 10:44:09 +0200 [thread overview]
Message-ID: <20030816084409.GA8038@suse.de> (raw)
Why is ->proc_info() called when the function pointer is NULL?
(none):/# mount proc
(none):/# cat /proc/scsi/
53c94 device_info scsi
(none):/# cat /proc/scsi/53c94/0
proc_scsi_read: 00000000 called
Oops: kernel access of bad area, sig: 11 [#1]
NIP: 00000000 LR: C00EC6C8 SP: C03BBE90 REGS: c03bbde0 TRAP: 0401 Not tainted
MSR: 40009030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c027b7e0[16] 'cat' Last syscall: 3
GPR00: C00EC6A0 C03BBE90 C027B7E0 C4705400 C43B5000 C03BBEC8 00000000 00000C00
GPR08: 00000000 00000000 C01C6E8F C01B0000 0000000D
Call trace:
[c007a254] proc_file_read+0xb8/0x2cc
[c004d97c] vfs_read+0xdc/0x128
[c004dbe8] sys_read+0x40/0x74
[c000780c] ret_from_syscall+0x0/0x4c
Segmentation fault
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
next reply other threads:[~2003-08-16 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 8:44 Olaf Hering [this message]
2003-08-16 10:06 ` scsi proc_info called unconditionally Christoph Hellwig
2003-08-16 17:00 ` Alan Cox
2003-08-17 8:09 ` Olaf Hering
2003-08-17 9:39 ` Christoph Hellwig
2003-08-17 9:56 ` Alan Cox
2003-08-17 10:07 ` Christoph Hellwig
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=20030816084409.GA8038@suse.de \
--to=olh@suse.de \
--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