From: David Sterba <dsterba@suse.cz>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.cz,
Lennart Poettering <lennart@poettering.net>
Subject: Re: btrfs_inode_item's otime?
Date: Fri, 9 Jan 2015 17:11:42 +0100 [thread overview]
Message-ID: <20150109161142.GC3685@twin.jikos.cz> (raw)
In-Reply-To: <2188846.ArnMyWRJKN@quad>
On Thu, Jan 08, 2015 at 09:52:30PM +1100, Chris Samuel wrote:
> Sorry for the delay, took a while to poke around the code to figure
> out possible ways it would get done (and what the right structure was).
No delay noticed :)
> > Set the otime in btrfs_new_inode after the call to fill_inode_item.
> Unfortunately I won't have a test system to try this on for a little while.
>
>
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index e687bb0..60bcc72 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -5835,6 +5835,11 @@ static struct inode *btrfs_new_inode(struct btrfs_trans_handle *trans,
> sizeof(*inode_item));
> fill_inode_item(trans, path->nodes[0], inode_item, inode);
>
> + /*
> + * Set the creation time on the inode.
> + */
> + btrfs_set_stack_timespec_sec( &inode.otime, cur_time.tv_sec );
Drop the spaces after/before parens and also set usec the same way.
There's no such thing as 'current_time', only CURRENT_TIME but that
cannot be used directly as a structure.
Given that the mtime is set a few lines above, copy the tv_sec and
tv_usec from there.
> +
> if (name) {
> ref = btrfs_item_ptr(path->nodes[0], path->slots[0] + 1,
> struct btrfs_inode_ref);
>
next prev parent reply other threads:[~2015-01-09 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 17:21 btrfs_inode_item's otime? Lennart Poettering
2015-01-06 11:47 ` Chris Samuel
2015-01-06 12:43 ` Chris Samuel
2015-01-06 18:41 ` David Sterba
2015-01-08 10:52 ` Chris Samuel
2015-01-09 16:11 ` David Sterba [this message]
2015-01-15 10:48 ` David Sterba
2015-01-16 4:47 ` Chris Samuel
2015-01-06 18:26 ` David Sterba
2015-01-07 13:57 ` Lennart Poettering
2015-01-07 14:42 ` Christoph Hellwig
2015-01-10 10:13 ` Martin Steigerwald
2015-01-10 10:17 ` Christoph Hellwig
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=20150109161142.GC3685@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=chris@csamuel.org \
--cc=lennart@poettering.net \
--cc=linux-btrfs@vger.kernel.org \
/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).