On Monday 09 September 2013 at 12:44:01, Edward wrote: > On 09/06/2013 07:36 AM, Ivan Shapovalov wrote: > > Hi Edward! > > > > I'm sorry for the silence... The summer, as it usually happens, turned out to > > be not-easier-than-studying-days (personal life and all), so unfortunately > > there is not much progress with TRIM implementation for reiser4. There is some > > code, but it's stability is zero. > > > > Anyway, here is my usual attempt to port reiser4 to next kernel. 3.11 got a > > significant API change (readdir() of file_operations changed to iterate()), > > and I'm unsure if I done that correctly. But it works, unlike TRIM. :) > > > Cool. Thanks!!! > > > > > > (FYI, iterate() differs from readdir() mostly in that it works with a copy of > > f_pos instead of with f->f_pos directly.) > > > AFAIK they fixed races in readdir() and friends. > I'll take a look at this more carefully... Yes, I've seen that reason. I'd be grateful if you could check my patch - because, again, I could have easily missed something wrt. locking and whether we can modify f->f_pos in the code that fixes it up when entries are inserted/removed. - Ivan > > > Edward. -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
