Quoting Josef Bacik (2013-07-01 08:54:35) > On Tue, Jun 04, 2013 at 06:17:54PM -0400, Zach Brown wrote: > > Hi gang, > > > > I finally sat down to fix that readdir hang that has been in the back > > of my mind for a while. I *hope* that the fix is pretty simple: just > > don't manufacture a fake f_pos, I *think* we can abuse f_version as an > > indicator that we shouldn't return entries. Does this look reasonable? > > > > We still have the problem that we can generate valid large f_pos values > > that can confuse 32bit userspace, but that's a different problem. I > > think we'll want filldir generation of EOVERFLOW like what exists for > > large inodes. > > > > The rest of the patches are cleanups that I saw when absorbing the > > code. It's all lightly tested with xfstests but it wouldn't surprise > > me if I missed something so review is appreciated. > > > > Thanks! > > > > One of these patches is making new entries not show up in readdir. This was > discovered while running stress.sh overnight, it complained about files not > matching but when they were checked the files matched. Dropping the entire > series made stress.sh run fine. So I'm dropping these for the next merge > window > but I'll dig into it and try and figure out what was causing the problem.
Unfortunately I've only triggered this on flash, and the run takes about two hours to trigger. Trying now with some extra printks to see if I can nail it down -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
