On Wed, Jun 07, 2006 at 11:50:31AM -0400, Peter Staubach wrote: > The Red Hat BZ number is 193621. "You are not authorized to access bug #193621", it tells me.... > The description is that when zero length files are copied, even over > an existing zero length file, the mtime on the target file does not > change. Is the server-side patch sufficient on its own? --b. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [NFS] [PATCH] NFS server does not update mtime on setattr request
- From: Peter Staubach <[email protected]>
- Re: [NFS] [PATCH] NFS server does not update mtime on setattr request
- References:
- [PATCH] NFS server does not update mtime on setattr request
- From: Peter Staubach <[email protected]>
- Re: [PATCH] NFS server does not update mtime on setattr request
- From: Trond Myklebust <[email protected]>
- Re: [PATCH] NFS server does not update mtime on setattr request
- From: Peter Staubach <[email protected]>
- Re: [NFS] [PATCH] NFS server does not update mtime on setattr request
- From: "J. Bruce Fields" <[email protected]>
- Re: [NFS] [PATCH] NFS server does not update mtime on setattr request
- From: Peter Staubach <[email protected]>
- Re: [NFS] [PATCH] NFS server does not update mtime on setattr request
- From: "J. Bruce Fields" <[email protected]>
- Re: [NFS] [PATCH] NFS server does not update mtime on setattr request
- From: Peter Staubach <[email protected]>
- [PATCH] NFS server does not update mtime on setattr request
- Prev by Date: Re: [PATCH 2/7] AMSO1100 Low Level Driver.
- Next by Date: booting without initrd
- Previous by thread: Re: [NFS] [PATCH] NFS server does not update mtime on setattr request
- Next by thread: Re: [NFS] [PATCH] NFS server does not update mtime on setattr request
- Index(es):
 |