From: Andi Kleen <ak@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
"Robin H. Johnson" <robbat2@gentoo.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tmpfs: time granularity fix for [acm]time going backwards
Date: Tue, 13 Jun 2006 05:38:33 +0200 [thread overview]
Message-ID: <200606130538.33160.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0606122146090.23556@blonde.wat.veritas.com>
> This patch should probably be included for 2.6.17, despite how long the
> bug has been around. It's a one-liner, with no side-effects.
Agreed - it's obviously correct and a nasty little problem.
Should be in 2.6.17.
-Andi
>
> mm/shmem.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- 2.6.17-rc6-git/mm/shmem.c
> +++ linux/mm/shmem.c
> @@ -2102,6 +2102,7 @@ static int shmem_fill_super(struct super
> sb->s_blocksize_bits = PAGE_CACHE_SHIFT;
> sb->s_magic = TMPFS_MAGIC;
> sb->s_op = &shmem_ops;
> + sb->s_time_gran = 1;
>
> inode = shmem_get_inode(sb, S_IFDIR | mode, 0);
> if (!inode)
>
next prev parent reply other threads:[~2006-06-13 3:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 11:54 [PATCH] tmpfs time granularity fix for [acm]time going backwards. Also VFS time granularity bug on creat(). (Repost, more content) Robin H. Johnson
2006-06-11 18:10 ` Hugh Dickins
2006-06-12 5:10 ` Robin H. Johnson
2006-06-12 7:19 ` Jan Engelhardt
2006-06-12 19:24 ` Hugh Dickins
2006-06-12 20:50 ` [PATCH] tmpfs: time granularity fix for [acm]time going backwards Hugh Dickins
2006-06-13 3:38 ` Andi Kleen [this message]
2006-06-12 12:22 ` [PATCH] tmpfs time granularity fix for [acm]time going backwards. Also VFS time granularity bug on creat(). (Repost, more content) Andi Kleen
2006-06-12 19:38 ` Hugh Dickins
2006-06-13 3:49 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200606130538.33160.ak@suse.de \
--to=ak@suse.de \
--cc=hugh@veritas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robbat2@gentoo.org \
--cc=torvalds@osdl.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).