#ifndef _UDF_I_H #define _UDF_I_H struct extent_position { struct buffer_head *bh; uint32_t offset; struct kernel_lb_addr block; }; struct udf_ext_cache { /* Extent position */ struct extent_position epos; /* Start logical offset in bytes */ loff_t lstart; }; /* * The i_data_sem and i_mutex serve for protection of allocation information * of a regular files and symlinks. This includes all extents belonging to * the file/symlink, a fact whether data are in-inode or in external data * blocks, preallocation, goal block information... When extents are read, * i_mutex or i_data_sem must be held (for reading is enough in case of * i_data_sem). When extents are changed, i_data_sem must be held for writing * and also i_mutex must be held. * * For directories i_mutex is used for all the necessary protection. */ struct udf_inode_info { struct timespec i_crtime; /* Physical address of inode */ struct kernel_lb_addr i_location; __u64 i_unique; __u32 i_lenEAttr; __u32 i_lenAlloc; __u64 i_lenExtents; __u32 i_next_alloc_block; __u32 i_next_alloc_goal; __u32 i_checkpoint; unsigned i_alloc_type : 3; unsigned i_efe : 1; /* extendedFileEntry */ unsigned i_use : 1; /* unallocSpaceEntry */ unsigned i_strat4096 : 1; unsigned reserved : 26; union { struct short_ad *i_sad; struct long_ad *i_lad; __u8 *i_data; } i_ext; struct rw_semaphore i_data_sem; struct udf_ext_cache cached_extent; /* Spinlock for protecting extent cache */ spinlock_t i_extent_cache_lock; struct inode vfs_inode; }; static inline struct udf_inode_info *UDF_I(struct inode *inode) { return container_of(inode, struct udf_inode_info, vfs_inode); } #endif /* _UDF_I_H) */ 28ca52a977d7b0b0159fee4b'>refslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2017-02-08 14:30:53 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-02-08 15:41:43 -0800
commit0911d0041c22922228ca52a977d7b0b0159fee4b (patch)
treeecd0e2bd3ec2f1e934409a43dd3b0798860c7d8b /include
parented5bd7dc88edf4a4a9c67130742b1b59aa017a5f (diff)
mm: avoid returning VM_FAULT_RETRY from ->page_mkwrite handlers
Some ->page_mkwrite handlers may return VM_FAULT_RETRY as its return code (GFS2 or Lustre can definitely do this). However VM_FAULT_RETRY from ->page_mkwrite is completely unhandled by the mm code and results in locking and writeably mapping the page which definitely is not what the caller wanted. Fix Lustre and block_page_mkwrite_ret() used by other filesystems (notably GFS2) to return VM_FAULT_NOPAGE instead which results in bailing out from the fault code, the CPU then retries the access, and we fault again effectively doing what the handler wanted. Link: http://lkml.kernel.org/r/20170203150729.15863-1-jack@suse.cz Signed-off-by: Jan Kara <jack@suse.cz> Reported-by: Al Viro <viro@ZenIV.linux.org.uk> Reviewed-by: Jinshan Xiong <jinshan.xiong@intel.com> Cc: Matthew Wilcox <willy@infradead.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include')
-rw-r--r--include/linux/buffer_head.h4
1 files changed, 1 insertions, 3 deletions
diff --git a/include/linux/buffer_head.h b/include/linux/buffer_head.h