From: Neil Brown <neilb@suse.de>
To: Jeff Layton <jlayton@redhat.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, nfs@lists.sourceforge.net
Subject: Re: [PATCH] nfs-utils: make auth_reload respect sub-second timestamps on etab
Date: Thu, 3 May 2007 10:55:37 +1000 [thread overview]
Message-ID: <17977.13065.307535.484372@notabene.brown> (raw)
In-Reply-To: message from Jeff Layton on Thursday April 26
On Thursday April 26, jlayton@redhat.com wrote:
>
> This patch seems to fix the problem as well. mountd holds the etab open, but
> doesn't actually do any I/O on that fd. This makes sure that the inode number
> of the new etab file won't be the same as the current version that mountd is
> aware of. I also added a comment to xtab_write to warn people who might
> consider changing how the files are written.
>
> We might also consider adding back in some of the mtime logic to try and
> catch programs that edit the file in place, but I'm not sure if that's
> worthwhile.
I agree.
>
> Neil, what do you think?
I was about to say "fine", but then saw the problem.
Because of the way get_exportlist uses the return value, that value
needs to unique over all time (or close to it). So returning the
inode number won't work (as we have seen that ext3 cycles between
two).
A simple event counter could be returned though, which would give
something unique to get_exportlist.
NeilBrown
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-05-03 0:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 17:39 [PATCH] nfs-utils: make auth_reload respect sub-second timestamps on etab Jeff Layton
2007-04-25 18:09 ` Jeff Layton
2007-04-25 20:13 ` Jeff Layton
2007-04-25 21:29 ` Chuck Lever
2007-04-26 4:56 ` Neil Brown
2007-04-26 12:05 ` Jeff Layton
2007-04-26 16:23 ` Jeff Layton
2007-04-26 16:58 ` J. Bruce Fields
2007-04-26 17:00 ` Jeff Layton
2007-04-26 17:24 ` J. Bruce Fields
2007-04-26 18:29 ` Jeff Layton
2007-05-03 0:55 ` Neil Brown [this message]
2007-05-03 11:58 ` Jeff Layton
2007-05-03 12:11 ` Jeff Layton
2007-04-26 17:33 ` Jeff Layton
2007-04-26 12:35 ` J. Bruce Fields
2007-04-26 4:50 ` Neil Brown
2007-04-26 11:50 ` 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=17977.13065.307535.484372@notabene.brown \
--to=neilb@suse.de \
--cc=bfields@fieldses.org \
--cc=jlayton@redhat.com \
--cc=nfs@lists.sourceforge.net \
/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