linux-kernel - question on kernel rwsem behaviour

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]

Date:	Fri, 21 Sep 2007 09:38:44 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	linux-kernel@...r.kernel.org
Subject: question on kernel rwsem behaviour

Hi all,

I just had a quick question on read-write semaphore semantics.  Suppose 
someone holds a sema for reading, then someone else tries to aquire it 
for writing, and blocks.  Finally, a third code path tries to aquire it 
for reading.

Does this third code path get the sema, or does it wait for the writer?

Based on looking at the implementation it seems like it waits, but I'd 
like to confirm that.

Thanks,

Chris
-
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/