linux-ext4 - a question for i_inode's i

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <2014bcab0809190021qbca7bect601c891c2db197cf@mail.gmail.com>
Date:	Fri, 19 Sep 2008 16:21:44 +0900
From:	"È«½Å shin hong" <hongshin@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: a question for i_inode's i_size in ext2

Dear ext2 maintainers

  I have a question of inode's i_size. I found that it is hard to find
any consistent synchronization mechanism that protects inode's i_size
field.
  Is there any lock or synchronization mechanism that consistently
protects i_size fields of inode objects to avoid data race?
  In inode's definition in /include/linux/fs.h, there is comment that
i_lock protects i_size but it is not clear.

Sincerely
Shin Hong
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html