lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 5 Jul 2010 15:15:06 +0300 From: Artem Bityutskiy <dedekind1@...il.com> To: Al Viro <viro@...IV.linux.org.uk> Cc: LKML <linux-kernel@...r.kernel.org>, linux-fsdevel@...r.kernel.org Subject: [PATCHv6 8/9] VFS: rename s_dirt to s_dirty From: Artem Bityutskiy <Artem.Bityutskiy@...ia.com> ... in order to make sure no one accesses the "s_dirt" flag direclty - this should help to identify build errors earlier. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@...ia.com> --- include/linux/fs.h | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/include/linux/fs.h b/include/linux/fs.h index 20d8cb0..1c11e36 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h @@ -1319,7 +1319,7 @@ extern spinlock_t sb_lock; struct super_block { struct list_head s_list; /* Keep this first */ dev_t s_dev; /* search index; _not_ kdev_t */ - unsigned char s_dirt; + unsigned char s_dirty; unsigned char s_blocksize_bits; unsigned long s_blocksize; loff_t s_maxbytes; /* Max file size */ @@ -1785,15 +1785,15 @@ extern void simple_set_mnt(struct vfsmount *mnt, struct super_block *sb); static inline void sb_mark_dirty(struct super_block *sb) { - sb->s_dirt = 1; + sb->s_dirty = 1; } static inline void sb_mark_clean(struct super_block *sb) { - sb->s_dirt = 0; + sb->s_dirty = 0; } static inline int sb_is_dirty(struct super_block *sb) { - return sb->s_dirt; + return sb->s_dirty; } /* Alas, no aliases. Too much hassle with bringing module.h everywhere */ -- 1.7.0.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists