On Mon, Jan 18, 2010 at 12:26 PM, Marc Aurele La France <[email protected]> wrote: > On Sun, 17 Jan 2010, Simon Wilkinson wrote: >> >> On 17 Jan 2010, at 13:48, Marc Aurele La France wrote: > >>> Any chance of incorporating these into stable? > >> When we last discussed pullups for 1.4.12, we decided that these were >> too high risk for that release (the changes appeared very late in the >> release cycle). MS_NOATIME is sufficiently large that it doesn't appear >> to conflict with any inode flags, up to and including Linus's current >> kernel, so there doesn't appear to be a risk associated with not taking >> them this time round. > > Only one more inode flag is needed to create a conflict. Whether or not > this occurs before 1.4.13 is released is a risk I gather you are willing to > take. I think it's better to be pro-active.
The question is "will it happen in a kernel 1.4.12 also doesn't support, making the issue somewhat less urgent?". There's a tradeoff in risks here. We obviously have a bit more flexibility than if we had a fixed schedule of releases. > I can see your point if, and only if, AFS is ever changed to provide proper > access times. It may well be, but... > Otherwise, I don't see how eliminating pointless traffic on the wire can > create a problem. You're probably right. _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
