From: "Jan Blunck" <jblunck@suse.de>
To: "Dave Kleikamp" <shaggy@linux.vnet.ibm.com>
Cc: "Jens Nie" <JNie@roseninspection.net>, linux-fsdevel@vger.kernel.org
Subject: Re: Possible bug in ext3 filesystem
Date: Thu, 4 Jan 2007 22:39:13 +0100 [thread overview]
Message-ID: <4de7f8a60701041339g24bc2cf9ub55b0d5e64eda22b@mail.gmail.com> (raw)
In-Reply-To: <1167939495.15090.30.camel@kleikamp.austin.ibm.com>
On 1/4/07, Dave Kleikamp <shaggy@linux.vnet.ibm.com> wrote:
> On Thu, 2007-01-04 at 12:34 +0100, Jens Nie wrote:
> > I think i found a bug in the ext3 filesystem. It deals with
> > dereferencing symlinks. I have installed a fresh openSUSE 10.2 on an
> > ext3 filesystem.
No, it seems to be a bug in the coreutils.
> I did a little playing around with strace and I suspect that it may have
> something to do with ext3 returning DT_LNK to the filldir routine (which
> gets returned through getdents64). A lot of file systems always return
> DT_UNKNOWN. Maybe ls is handling the DT_UNKNOWN case alright, but not
> the DT_LNK case. (When DT_UNKNOWN is returned, ls calls stat64() which
> would identify the symlink as a directory rather than a symlink.)
I guess your analysis is right. The problem is that ls only calls
stat() on DT_UNKNOWN entries but it should call it on DT_LNK too.
> > I reported this on the opensuse mailing list first. Someone there was
> > kind enough to point me directly to this list.
They forgot to tell you that not every bug is a kernel bug ;)
I opened a bug in bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=231916
prev parent reply other threads:[~2007-01-04 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 11:34 Possible bug in ext3 filesystem Jens Nie
2007-01-04 17:47 ` Theodore Tso
2007-01-04 19:38 ` Dave Kleikamp
2007-01-04 21:39 ` Jan Blunck [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=4de7f8a60701041339g24bc2cf9ub55b0d5e64eda22b@mail.gmail.com \
--to=jblunck@suse.de \
--cc=JNie@roseninspection.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
/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).