From: Ingo Molnar <mingo@elte.hu>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: isofs oops - d_splice_alias+0x1f (2.6.24-rc5-mm1)
Date: Thu, 3 Jan 2008 15:11:20 +0100 [thread overview]
Message-ID: <20080103141120.GC19363@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0801031550160.2076@sbz-30.cs.Helsinki.FI>
* Pekka J Enberg <penberg@cs.helsinki.fi> wrote:
> return ERR_PTR(-EACCES);
> }
> + if (is_bad_inode(inode)) {
> + unlock_kernel();
> + iput(inode);
> + return ERR_PTR(-ENOENT);
> + }
fs/isofs/rock.c:474 parse_rock_ridge_inode_internal() seems buggy too:
reloc =
isofs_iget(inode->i_sb,
ISOFS_I(inode)->i_first_extent,
0);
if (!reloc)
goto out;
it should probably do "!reloc || is_bad_inode(inode)" as well.
and there are about 5 other callsites as well that only check for a NULL
return.
perhaps the better fix would be to add this to inode.c:isofs_iget():
if (inode && (inode->i_state & I_NEW)) {
sb->s_op->read_inode(inode);
unlock_new_inode(inode);
if (s_bad_inode(inode))
inode = NULL;
}
?
Ingo
next prev parent reply other threads:[~2008-01-03 14:11 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 [this message]
2008-01-03 14:14 ` Al Viro
2008-01-03 14:11 ` Al Viro
2008-01-03 14:15 ` Jiri Slaby
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=20080103141120.GC19363@elte.hu \
--to=mingo@elte.hu \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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.