From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: isofs oops - d_splice_alias+0x1f (2.6.24-rc5-mm1)
Date: Sat, 5 Jan 2008 09:46:02 +0000 [thread overview]
Message-ID: <20080105094602.GI27894@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20080105013126.d90c4e09.akpm@linux-foundation.org>
On Sat, Jan 05, 2008 at 01:31:26AM -0800, Andrew Morton wrote:
> On Thu, 3 Jan 2008 14:10:33 +0000 Al Viro <viro@ZenIV.linux.org.uk> wrote:
>
> >
> > which would not manage to return ERR_PTR(-EIO), no matter what - it would
> > die on access to inode->i_state. I don't have -mm tree at hand, check if
> > there's anything affected in these areas. Perhaps somebody tried to pass
> > error values from isofs_iget() and forgot to update callers?
>
> Yep. Unlike 2.6.24-rc5-mm1, 2.6.24-rc6-mm1 has
>
> iget-stop-isofs-from-using-read_inode-fix-2.patch
> iget-stop-isofs-from-using-read_inode-fix-2-update.patch
>
> so hopefully this was all fixed.
Nope; missed by both; fix (and fix to fix) had been posted, but IMO it's
better to replace the entire sorry pile with new variant of patch dhowells
had posted - it has all fixes folded in.
prev parent reply other threads:[~2008-01-05 9:46 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
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 [this message]
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=20080105094602.GI27894@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jirislaby@gmail.com \
--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 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.