Andrew Morton <[email protected]> wrote: > set_page_dirty() will set I_DIRTY_PAGES only. ie: the inode has dirty > pagecache data. > > To tell the VFS that the inode itself is dirty one needs to run > mark_inode_dirty(). But what's the difference in this case? I don't need to write the inode back per se, and the inode attributes can be updated by the mechanism of data storage. David - 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: [PATCH 3/3] AFS: Implement basic file write support
- From: Andrew Morton <[email protected]>
- Re: [PATCH 3/3] AFS: Implement basic file write support
- References:
- Re: [PATCH 3/3] AFS: Implement basic file write support
- From: Andrew Morton <[email protected]>
- Re: [PATCH 3/3] AFS: Implement basic file write support
- From: Andrew Morton <[email protected]>
- [PATCH 1/3] AFS: Export a couple of core functions for AFS write support
- From: David Howells <[email protected]>
- [PATCH 3/3] AFS: Implement basic file write support
- From: David Howells <[email protected]>
- Re: [PATCH 3/3] AFS: Implement basic file write support
- From: David Howells <[email protected]>
- Re: [PATCH 3/3] AFS: Implement basic file write support
- Prev by Date: Re: [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS
- Next by Date: Re: [PATCH] Intel IXP4xx network drivers v.2 - Ethernet and HSS
- Previous by thread: Re: [PATCH 3/3] AFS: Implement basic file write support
- Next by thread: Re: [PATCH 3/3] AFS: Implement basic file write support
- Index(es):
 |