----- Original Message ----- | Here is a series of three patches that fix file timestamp related bugs: | | Revert "[fs] gfs2: Only refresh newer in-memory timestamps" | | It turns out that this commit didn't fix the actual bug | (https://bugzilla.redhat.com/show_bug.cgi?id=1304847), but only hid the | effect of the bug. In addition, it failed to initialize the mtime and | ctime | for I_NEW inodes, resulting in timestamp corruption. | | gfs2: Update file times after grabbing glock | | This fixes the actual bug in | https://bugzilla.redhat.com/show_bug.cgi?id=1304847, and | https://bugzilla.redhat.com/show_bug.cgi?id=1374861 and | https://bugzilla.redhat.com/show_bug.cgi?id=1375682 as well. | | gfs2: Initialize atime of I_NEW inodes | | It turned out that the atime also isn't properly initialized for I_NEW | inodes; this bug was introduced a long time ago, in | https://bugzilla.redhat.com/show_bug.cgi?id=462579. | | Thanks, | Andreas
Hi Andreas, This mailing list is normally only for upstream patches. Since the patch you're trying to revert is not in the upstream kernel, I can only assume this patch set is not for upstream. The concept looks good, but do you have patches for upstream? Regards, Bob Peterson Red Hat File Systems
