From: Johnny Mnemonic <johnny@themnemonic.org>
To: linux-kernel@vger.kernel.org
Subject: Fwd: Re: bug in tmpfs
Date: Wed, 8 May 2002 19:03:29 +0200 [thread overview]
Message-ID: <20020508170024.RTDY6993.fep23-svc.tin.it@there> (raw)
---------- Forwarded Message ----------
Subject: Re: bug in tmpfs
Date: 08 May 2002 09:17:21 +0200
From: Christoph Rohland <cr@sap.com>
To: Johnny Mnemonic <johnny@themnemonic.org>
> I've noticed the following wrong behaviour on tmpfs:
>
> (running kernel 2.4.18)
>
> [johnny@revenge johnny]$ cd /mnt/shm
> [johnny@revenge shm]$ rm -rf W
> [johnny@revenge shm]$ mkdir W
> [johnny@revenge shm]$ cd W
> [johnny@revenge W]$ touch MYFILE
> [johnny@revenge W]$ ln -s X Y
> [johnny@revenge W]$ ls -l
> total 0
> -rw-rw-r-- 1 johnny johnny 0 May 7 19:37 MYFILE
> -rw-rw-r-- 1 johnny johnny 0 May 7 19:37 MYFILE
> lrwxrwxrwx 1 johnny johnny 1 May 7 19:37 Y -> X
> [johnny@revenge W]$ ls -l
> total 0
> -rw-rw-r-- 1 johnny johnny 0 May 7 19:37 MYFILE
> lrwxrwxrwx 1 johnny johnny 1 May 7 19:37 Y -> X
> [johnny@revenge W]$
>
> This bug is reproducible in most ways, when you create a
> non-existent symlink, the first ls will always show up two "MYFILE",
> while the second and further one won't.
This is probably a misbehaviour of the general cfs layer on which the
tmpfs directory handling relies. Further on my time nowaday is totally
sucked up by my job. So I can't look into this myself.
Please report this bug to the Linux Kernel Mailing list.
Greetings
Christoph
-------------------------------------------------------
Anyone would like to track this bug before 2.4.19 release?
Regards
--
Johnny
next reply other threads:[~2002-05-08 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 17:03 Johnny Mnemonic [this message]
2002-05-08 21:30 ` Charles A. Clinton
2002-05-09 20:08 ` [PATCH] 2.14.19-pre8 " Charles A. Clinton
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=20020508170024.RTDY6993.fep23-svc.tin.it@there \
--to=johnny@themnemonic.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®