Displaying 2 results from an estimated 2 matches for "next_hash".
Did you mean:
new_hash
2003 Mar 05
1
RE: [Ext2-devel] Re: ext3 htree brelse problems look to be fixed!
...c".
Not have chance to run it on a NFS server yet.
Do you have more information about the cache trashing
bug?
Regards,
Chris
===== dir.c 1.5 vs edited =====
--- 1.5/fs/ext3/dir.c Wed Oct 2 01:24:11 2002
+++ edited/dir.c Sat Mar 1 23:45:04 2003
@@ -450,8 +450,10 @@
&info->next_hash);
if (ret < 0)
return ret;
- if (ret == 0)
+ if (ret == 0) {
+ filp->f_pos = -1;
break;
+ }
info->curr_node = rb_get_first(&info->root);
}
> -----Original Message-----
> From: Daniel Phillips [mailto:phillips@arcor.de]
> Sent: Wednesday, Mar...
2004 Dec 05
1
BUG in fs/ext3/dir.c
...info->curr_node = rb_first(&info->root);
@@ -492,7 +495,7 @@
info->curr_minor_hash = fname->minor_hash;
if (call_filldir(filp, dirent, filldir, fname))
break;
-
+next_entry:
info->curr_node = rb_next(info->curr_node);
if (!info->curr_node) {
if (info->next_hash == ~0) {
Regards,
Holger
PS: Please CC me since I am not on this list.
-------------- next part --------------
#include <stdio.h>
#include <string.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <dirent.h>
#include <fcntl.h>
#...