From: jblunck@suse.de
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: viro@ftp.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [RFC,PATCH] libfs dcache_readdir() and dcache_dir_lseek() bugfix
Date: Mon, 7 Nov 2005 11:17:10 +0100 [thread overview]
Message-ID: <20051107101710.GB7932@hasse.suse.de> (raw)
In-Reply-To: <E1EY4Hp-0004hf-00@dorka.pomaz.szeredi.hu>
On Fri, Nov 04, Miklos Szeredi wrote:
>
> Your patch is not a solution, since readdir will remain nonconforming.
> It is basically a workaround for a bug in glibc.
Updating the glibc is no solution because this isn't possible here. And I still
have the opinion that it is the filesystems job to remember the right
offset. At least this is what SuSV3 is telling me.
> It makes readdir
> nonconforming in a different way, but the end result in not
> necessarily better.
Hmm, yes you are right.
>
> If you manage to make dcache_readdir conform to SUS without overly
> bloating the implementation, that's fine.
Will look into that, if its possible.
Regards,
Jan Blunck
--
Jan Blunck jblunck@suse.de
SuSE LINUX AG - A Novell company
Maxfeldstr. 5 +49-911-74053-608
D-90409 Nürnberg http://www.suse.de
next prev parent reply other threads:[~2005-11-07 10:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 11:38 [RFC,PATCH] libfs dcache_readdir() and dcache_dir_lseek() bugfix jblunck
2005-11-04 11:51 ` Al Viro
2005-11-04 12:20 ` jblunck
2005-11-04 12:56 ` Miklos Szeredi
2005-11-04 13:18 ` jblunck
2005-11-04 13:31 ` Miklos Szeredi
2005-11-04 15:11 ` jblunck
2005-11-04 15:16 ` Jörn Engel
2005-11-04 15:34 ` jblunck
2005-11-04 15:45 ` Jörn Engel
2005-11-04 15:38 ` Miklos Szeredi
2005-11-04 15:32 ` Miklos Szeredi
2005-11-04 15:46 ` jblunck
2005-11-04 15:55 ` Miklos Szeredi
2005-11-04 16:04 ` jblunck
2005-11-04 16:19 ` Miklos Szeredi
2005-11-07 10:17 ` jblunck [this message]
2005-11-04 16:27 ` Al Viro
2005-11-04 16:27 ` Trond Myklebust
2005-11-04 16:39 ` Miklos Szeredi
2005-11-04 16:55 ` Rob Landley
2005-11-07 10:06 ` jblunck
2005-11-04 12:52 ` Jörn Engel
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=20051107101710.GB7932@hasse.suse.de \
--to=jblunck@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@ftp.linux.org.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 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.