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]
Date:	Mon, 09 Jun 2008 15:42:55 -0500
From:	Eric Sandeen <>
To:	ext4 development <>
CC:	Alex Tomas <>
Subject: __set_bit for BH flags in ext4_ext_get_blocks?

I was wondering why ext4_ext_get_blocks calls things like:

__set_bit(BH_Unwritten, &bh_result->b_state);
__set_bit(BH_New, &bh_result->b_state);
__set_bit(BH_Mapped, &bh_result->b_state);

instead of set_buffer_unwritten, etc.

Is there any reason it's calling __set_bit instead of set_bit (via the
BUFFER_FNS macros)?

To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists