From: Andi Kleen <ak@suse.de>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, hugh@veritas.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tmpfs time granularity fix for [acm]time going backwards. Also VFS time granularity bug on creat(). (Repost, more content)
Date: 12 Jun 2006 14:22:50 +0200 [thread overview]
Message-ID: <p73ac8isgv9.fsf@verdi.suse.de> (raw)
In-Reply-To: <20060611115421.GE26475@curie-int.vc.shawcable.net>
"Robin H. Johnson" <robbat2@gentoo.org> writes:
> [Please CC me on replies].
>
> 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. Good catch.
That was my bug when doing the conversion - but for my defense
having file systems outside fs/* is error prone.
Can we perhaps move tmpfs or at least the fs parts of shmem.c
into fs/ in the future? (the file is too big anyways)
-Andi
next prev parent reply other threads:[~2006-06-12 12:22 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
2006-06-12 12:22 ` Andi Kleen [this message]
2006-06-12 19:38 ` [PATCH] tmpfs time granularity fix for [acm]time going backwards. Also VFS time granularity bug on creat(). (Repost, more content) 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=p73ac8isgv9.fsf@verdi.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=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