Hi, today a sizable portion of the "struct file_operations" variables in the kernel are const, but by far not all. Nor are any of the struct inode_operations const. Marking these read-only datastructures const has the advantage of reducing false sharing of these, often hot, datastructures. In addition there have been cases where drivers or filesystems accidentally and incorrectly wrote to such a struct forgetting that it's a shared datastructure. By marking these const, the compiler will warn/error on such instances. The series is split up for size, there isn't really any logical order for such a simple search-and-replace operation. Greetings, Arjan van de Ven - 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:
- [patch 12/12] mark struct inode_operations const 3
- From: Arjan van de Ven <[email protected]>
- [patch 11/12] mark struct inode_operations const 2
- From: Arjan van de Ven <[email protected]>
- [patch 10/12] mark struct inode_operations const 1
- From: Arjan van de Ven <[email protected]>
- [patch 09/12] mark struct file_operations const 9
- From: Arjan van de Ven <[email protected]>
- [patch 07/12] mark struct file_operations const 7
- From: Arjan van de Ven <[email protected]>
- [patch 08/12] mark struct file_operations const 8
- From: Arjan van de Ven <[email protected]>
- [patch 06/12] mark struct file_operations const 6
- From: Arjan van de Ven <[email protected]>
- [patch 05/12] mark struct file_operations const 5
- From: Arjan van de Ven <[email protected]>
- [patch 04/12] mark struct file_operations const 4
- From: Arjan van de Ven <[email protected]>
- [patch 03/12] mark struct file_operations const 3
- From: Arjan van de Ven <[email protected]>
- [patch 02/12] mark struct file_operations const 2
- From: Arjan van de Ven <[email protected]>
- [patch 01/12] mark struct file_operations const 1
- From: Arjan van de Ven <[email protected]>
- [patch 00/12] Fix ppc64's writing to struct file_operations
- From: Arjan van de Ven <[email protected]>
- [patch 12/12] mark struct inode_operations const 3
- Prev by Date: Re: [patch 09/20] XEN-paravirt: dont export paravirt_ops structure, do individual functions
- Next by Date: [patch 00/12] Fix ppc64's writing to struct file_operations
- Previous by thread: How to mmap a shadow framebuffer in virtual memory
- Next by thread: [patch 00/12] Fix ppc64's writing to struct file_operations
- Index(es):
 |