Btw, while this patch made it to mainline it never went into the oss cvs tree (and thus probably the ptools tree). There also are a lot of other difference between the trees, I'll see how to get them
Christoph Hellwig wrote: Btw, while this patch made it to mainline it never went into the oss cvs tree (and thus probably the ptools tree). There also are a lot of other difference between the trees,
I think I have most of them covered: - log reace - the endianess helpers patch I sent a note out about - the mnt_want_write patches I've sent today - just yesterday the creds preparation in mainline
Christoph Hellwig wrote: On Fri, Aug 15, 2008 at 11:25:29AM +1000, Lachlan McIlroy wrote: Christoph Hellwig wrote: Btw, while this patch made it to mainline it never went into the oss cvs tree (and t
No, sorry for the stupid typo. I meant now with kgdb in maybe the kdb folks can get their act together and try to submit it, at which point xfsidbg could go upstream. Ok, I'll prepare something. Yeah
Btw, while this patch made it to mainline it never went into the oss cvs tree (and thus probably the ptools tree). There also are a lot of other difference between the trees, I'll see how to get them
Christoph Hellwig wrote: Btw, while this patch made it to mainline it never went into the oss cvs tree (and thus probably the ptools tree). There also are a lot of other difference between the trees,
I think I have most of them covered: - log reace - the endianess helpers patch I sent a note out about - the mnt_want_write patches I've sent today - just yesterday the creds preparation in mainline
Christoph Hellwig wrote: On Fri, Aug 15, 2008 at 11:25:29AM +1000, Lachlan McIlroy wrote: Christoph Hellwig wrote: Btw, while this patch made it to mainline it never went into the oss cvs tree (and t
No, sorry for the stupid typo. I meant now with kgdb in maybe the kdb folks can get their act together and try to submit it, at which point xfsidbg could go upstream. Ok, I'll prepare something. Yeah
When we release the iclog, we do an atomic_dec_and_lock to determine if we are the last reference to enable update of log headers and writeout. however, in xlog_state_get_iclog_space() we need to che
Yeah, looks good. Thanks. (My personal preference is for reversing if/else than using ! as it is easier to read but whatever :) But will need Eric's result before checking it in. --Tim
Eric Sandeen wrote: Dave Chinner wrote: When we release the iclog, we do an atomic_dec_and_lock to determine if we are the last reference to enable update of log headers and writeout. however, in xlo
Thanks, Tim - I'll add the right tags and send it to Linus. It looked funny with one line in the upper branch, and I added the comment inside the if() because it wasn't obvious from the code (either
When we release the iclog, we do an atomic_dec_and_lock to determine if we are the last reference to enable update of log headers and writeout. however, in xlog_state_get_iclog_space() we need to che
Yeah, looks good. Thanks. (My personal preference is for reversing if/else than using ! as it is easier to read but whatever :) But will need Eric's result before checking it in. --Tim