From: Jiri Slaby <jirislaby@gmail.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: isofs oops - d_splice_alias+0x1f (2.6.24-rc5-mm1)
Date: Thu, 03 Jan 2008 15:15:56 +0100 [thread overview]
Message-ID: <477CEE1C.7020005@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801031550160.2076@sbz-30.cs.Helsinki.FI>
On 01/03/2008 02:51 PM, Pekka J Enberg wrote:
> Hi Jiri,
>
> On Thu, 3 Jan 2008, Jiri Slaby wrote:
>> this happened, while playing with broken dvd.
>
> [snip]
>
>> Buffer I/O error on device sr0, logical block 5441
>> end_request: I/O error, dev sr0, sector 136
>> ISOFS: unable to read i-node block
>> Unable to handle kernel NULL pointer dereference at 00000000000000ad RIP:
>> [<ffffffff802a679f>] d_splice_alias+0x1f/0x100
>
> [snip]
>
>> Call Trace:
>> [<ffffffff880d2395>] :isofs:isofs_lookup+0x395/0x4a0
>> [<ffffffff802a565b>] d_alloc+0x2b/0x1d0
>> [<ffffffff8029a97c>] do_lookup+0x1ac/0x200
>
> Does the following patch fix it?
>
> Pekka
>
> [PATCH] isofs: check for bad inode in isofs_lookup
> From: Pekka Enberg <penberg@cs.helsinki.fi>
>
> If isofs_read_inode() fails to read one of the inode blocks from disk, it
> returns a bad inode.
>
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> ---
> fs/isofs/namei.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> Index: linux-2.6/fs/isofs/namei.c
> ===================================================================
> --- linux-2.6.orig/fs/isofs/namei.c
> +++ linux-2.6/fs/isofs/namei.c
> @@ -183,6 +183,11 @@ struct dentry *isofs_lookup(struct inode
> unlock_kernel();
> return ERR_PTR(-EACCES);
> }
> + if (is_bad_inode(inode)) {
> + unlock_kernel();
> + iput(inode);
> + return ERR_PTR(-ENOENT);
> + }
> }
> unlock_kernel();
> return d_splice_alias(inode, dentry);
Can't say, the DVD seems to be OK, I don't know what was wrong (as I can say,
this happened several times in the past yet and after reboot everything OK; I
suspect gnome auto mounter -- multiple machines, several DVD ROMs, same disk
with OS, similar errors, but that's too few to report).
next prev parent reply other threads:[~2008-01-03 14:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 13:23 isofs oops - d_splice_alias+0x1f (2.6.24-rc5-mm1) Jiri Slaby
2008-01-03 13:51 ` Pekka J Enberg
2008-01-03 14:11 ` Ingo Molnar
2008-01-03 14:14 ` Al Viro
2008-01-03 14:11 ` Al Viro
2008-01-03 14:15 ` Jiri Slaby [this message]
2008-01-04 10:47 ` Al Viro
2008-01-04 11:13 ` Dave Young
2008-01-04 11:25 ` Dave Young
2008-01-04 11:26 ` Al Viro
2008-01-04 12:24 ` David Howells
2008-01-04 12:35 ` Al Viro
2008-01-04 12:43 ` David Howells
2008-01-04 13:29 ` Ingo Molnar
2008-01-03 14:10 ` Al Viro
2008-01-05 9:31 ` Andrew Morton
2008-01-05 9:46 ` Al Viro
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=477CEE1C.7020005@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=viro@zeniv.linux.org.uk \
/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.