From: Jeremy Allison <jra-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/3] cifs: use CreationTime like an i_generation field
Date: Mon, 22 Nov 2010 12:59:17 -0800 [thread overview]
Message-ID: <20101122205917.GC7071@samba2> (raw)
In-Reply-To: <20101122153125.68ee4ee6-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
On Mon, Nov 22, 2010 at 03:31:25PM -0500, Jeff Layton wrote:
> On Mon, 22 Nov 2010 14:22:50 -0600
> Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > On Mon, Nov 22, 2010 at 1:55 PM, Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> >
> > > On Mon, 28 Jun 2010 07:10:12 -0400
> > > Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> > >
> > >
> > > Steve, can you clarify where we are with this patch? I originally sent
> > > this back in June. You and I discussed this at the CIFS plugfest and I
> > > had thought you had decided to merge it. It's still not in your tree
> > > however. Can you give a verdict on whether you're going to merge it and
> > > let me know when I can expect to see it in your tree if so?
> > >
> > >
> > Thanks for reminding me. I had forgotten to ask JRA about a question
> > on legacy Samba behavior. I remembered that older Samba
> > had problems with creation time - and was trying to remember what
> > the implication of using this patch with older Samba was.
> >
>
> All samba versions have issues with create times (at least on Linux
> anyway). They fake them, by using the ctime (which seems like an odd
> choice to me) in most cases.
New Samba's store create time in an xattr, so they can
return a reasonably valid create time value.
Jeremy.
next prev parent reply other threads:[~2010-11-22 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 11:10 [PATCH 0/3] cifs: tighten up cifs_iget matching criteria Jeff Layton
2010-06-28 11:10 ` [PATCH 1/3] cifs: don't allow cifs_iget to match inodes of the wrong type Jeff Layton
[not found] ` <1277723413-23769-1-git-send-email-jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-06-28 11:10 ` [PATCH 2/3] cifs: use CreationTime like an i_generation field Jeff Layton
[not found] ` <1277723413-23769-3-git-send-email-jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-06-28 13:26 ` Suresh Jayaraman
2010-06-28 13:47 ` Jeff Layton
2010-11-22 19:55 ` Jeff Layton
[not found] ` <AANLkTimtg0vFVQ5HGo+nq7rE=Z4Sob=z7LuVCMFgWdnv@mail.gmail.com>
[not found] ` <AANLkTimtg0vFVQ5HGo+nq7rE=Z4Sob=z7LuVCMFgWdnv-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-22 20:31 ` Jeff Layton
[not found] ` <20101122153125.68ee4ee6-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2010-11-22 20:59 ` Jeremy Allison [this message]
2010-12-07 1:55 ` Jeff Layton
2010-06-28 11:10 ` [PATCH 3/3] cifs: reduce false positives with inode aliasing serverino autodisable Jeff Layton
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=20101122205917.GC7071@samba2 \
--to=jra-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).