From: Linus Torvalds <torvalds@osdl.org>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Konstantin Boldyshev <konst@linuxassembly.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
<marcelo.tosatti@cyclades.com>
Subject: Re: minix fs corruption fix for 2.4
Date: Mon, 3 Nov 2003 09:50:16 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0311030949040.20373-100000@home.osdl.org> (raw)
In-Reply-To: <20031103171925.GH7665@parcelfarce.linux.theplanet.co.uk>
On Mon, 3 Nov 2003 viro@parcelfarce.linux.theplanet.co.uk wrote:
>
> Hmm... I would rather check for regular|directory|symlink explicitly -
> note that FIFO and socket can have junk in i_data.
Fair enough, that's how sysvfs does it too.
Committed and pushed out.
Thanks Konstantin,
Linus
next prev parent reply other threads:[~2003-11-03 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 13:21 minix fs corruption fix for 2.4 Konstantin Boldyshev
2003-11-03 16:55 ` Linus Torvalds
2003-11-03 17:19 ` viro
2003-11-03 17:50 ` Linus Torvalds [this message]
2003-11-04 6:30 ` Konstantin Boldyshev
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=Pine.LNX.4.44.0311030949040.20373-100000@home.osdl.org \
--to=torvalds@osdl.org \
--cc=konst@linuxassembly.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=viro@parcelfarce.linux.theplanet.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).