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 for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:	Fri, 26 Sep 2008 13:53:24 +0900
From:	"È«½Å shin hong" <hongshin@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: a question for i_inode's i_size in ext2

  Thank you for the answering.

  In ext2, it seems to me that inode's i_size field can be accessed
without holding i_mutex
  nor thorugh i_size_read function.

  For example, in ext2_update_inode() can be invoked without holding i_mutex.
  However, it freely access i_size field.

  Are these accesses can race with each others?


  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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ