From: Eric Paris <eparis@parisplace.org>
To: linux-kernel@vger.kernel.org
Cc: zippel@linux-m68k.org
Subject: Re: [PATCH] hfs: correct return value in hfs_fill_super()
Date: Thu, 16 Nov 2006 17:51:05 -0500 [thread overview]
Message-ID: <1163717465.22367.13.camel@localhost.localdomain> (raw)
In-Reply-To: <1163715533.22367.10.camel@localhost.localdomain>
On Thu, 2006-11-16 at 17:18 -0500, Eric Paris wrote:
> When an invalid hfs filesystem image is mounted it may cause a number of
> different oops. One filesystem image which triggers this problem can be
> found at:
>
Whoops, appears to be the same as the post from Eric Sandeen on tuesday
with subject
[PATCH] hfs_fill_super returns success even if no root inode
please disregard.
prev parent reply other threads:[~2006-11-16 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 22:18 [PATCH] hfs: correct return value in hfs_fill_super() Eric Paris
2006-11-16 22:51 ` Eric Paris [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=1163717465.22367.13.camel@localhost.localdomain \
--to=eparis@parisplace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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