Re: [patch 4/5] VFS: allow filesystems to implement atomic open+truncate

> > From: Miklos Szeredi <[email protected]>
> > 
> > Add a new attribute flag ATTR_OPEN, with the meaning: "truncation was
> > initiated by open() due to the O_TRUNC flag".
> > 
> > This way filesystems wanting to implement truncation within their
> > ->open() method can ignore such truncate requests.
> > 
> > This is a quick & dirty hack, but it comes for free.
> 
> Fine with me as it doesn't cause any active harm, but expect this to
> go away once the nfs intent mess is cleaned up and we'll get a real
> method for this kind of thing.

Sure.

Miklos
-
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/

---

• References:
  • [patch 0/5] VFS changes
    • From: Miklos Szeredi <[email protected]>
  • [patch 4/5] VFS: allow filesystems to implement atomic open+truncate
    • From: Miklos Szeredi <[email protected]>
  • Re: [patch 4/5] VFS: allow filesystems to implement atomic open+truncate
    • From: Christoph Hellwig <[email protected]>

• Prev by Date: Re: [patch 3/5] VFS: pass open file to ->xattr()
• Next by Date: Re: [PATCH 02/03] CM-x270: ITE 8152 PCI bridge support
• Previous by thread: Re: [patch 4/5] VFS: allow filesystems to implement atomic open+truncate
• Next by thread: Re: [patch 4/5] VFS: allow filesystems to implement atomic open+truncate
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]