Re: d_ino bug in //

2006-02-28 Thread Corinna Vinschen
On Feb 27 18:18, Eric Blake wrote: > > > > It looks like Corinna already nailed the issue, but for the > > archive's sake, my complaint was that under //, d_ino and > > st_ino did not match properly. With the 20060227 snapshot > > (or whenever the next one is), the same test program > > should no

Re: d_ino bug in //

2006-02-27 Thread Eric Blake
> Corinna Vinschen replied: > > I've applied a fix. > > I tried the fix in the 20060227 snapshot. > It did not fix the 'pwd' problems I noted in: > http://cygwin.com/ml/cygwin/2006-02/msg00933.html > > (If it wasn't meant to, then please pardon my ignorance.) There were two sets of bugs - one in

Re: d_ino bug in //

2006-02-27 Thread Christopher Faylor
On Mon, Feb 27, 2006 at 01:47:35PM -0700, Jerry D. Hedden wrote: >On Feb 27 17:22, Eric Blake wrote: >> It looks like d_ino is not being correctly populated within //. > >Corinna Vinschen replied: >> I've applied a fix. > >I tried the fix in the 20060227 snapshot. >It did not fix the 'pwd' problems

Re: d_ino bug in //

2006-02-27 Thread Jerry D. Hedden
On Feb 27 17:22, Eric Blake wrote: > It looks like d_ino is not being correctly populated within //. Corinna Vinschen replied: > I've applied a fix. I tried the fix in the 20060227 snapshot. It did not fix the 'pwd' problems I noted in: http://cygwin.com/ml/cygwin/2006-02/msg00933.html (If it wa

Re: d_ino bug in //

2006-02-27 Thread Eric Blake
> > It looks like Corinna already nailed the issue, but for the > archive's sake, my complaint was that under //, d_ino and > st_ino did not match properly. With the 20060227 snapshot > (or whenever the next one is), the same test program > should now output: Other directories that may have the

Re: d_ino bug in //

2006-02-27 Thread Christopher Faylor
On Mon, Feb 27, 2006 at 05:58:50PM +, Eric Blake wrote: >> >It looks like d_ino is not being correctly populated within //. >> >Running the program below on snapshot 20060220 produced: >> >> A (somewhat) simple test case (patent pending) is nice but it really >> should be accompanied with an e

Re: d_ino bug in //

2006-02-27 Thread Eric Blake
> >It looks like d_ino is not being correctly populated within //. > >Running the program below on snapshot 20060220 produced: > > A (somewhat) simple test case (patent pending) is nice but it really > should be accompanied with an explanation of the problem. How about > describing *in words* wha

Re: d_ino bug in //

2006-02-27 Thread Corinna Vinschen
On Feb 27 17:22, Eric Blake wrote: > It looks like d_ino is not being correctly populated within //. > Running the program below on snapshot 20060220 produced: > > $ ./foo > Searching for //eblake, inode 10556217422951964268 > entry 553: name match only (inode 14394969718775064264) > 2098 entries

Re: d_ino bug in //

2006-02-27 Thread Christopher Faylor
On Mon, Feb 27, 2006 at 05:22:57PM +, Eric Blake wrote: >It looks like d_ino is not being correctly populated within //. >Running the program below on snapshot 20060220 produced: A (somewhat) simple test case (patent pending) is nice but it really should be accompanied with an explanation of t

d_ino bug in //

2006-02-27 Thread Eric Blake
It looks like d_ino is not being correctly populated within //. Running the program below on snapshot 20060220 produced: $ ./foo Searching for //eblake, inode 10556217422951964268 entry 553: name match only (inode 14394969718775064264) 2098 entries processed $ cat foo.c #include #include #includ