linux-kernel - A question about Byte range locking.

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>] [day] [month] [year] [list]

Message-ID: <3a9148b90912200422j1b0b008dp90d0e0cd44ccf31d@mail.gmail.com>
Date:	Sun, 20 Dec 2009 17:52:23 +0530
From:	Dhruv Matani <dhruvbird@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: A question about Byte range locking.

Hello,
  I was reading the kernel code to try and figure out how byte range
locking is implemented inside the kernel, and it looks as if it is
implemented using linked lists of locks which store the range locked
and the type of lock. Am I right??

-- 
   -Dhruv Matani.
http://www.geocities.com/dhruvbird/

"How do you know when someone's crazy?"
"Well, you don't always. Depends on how many people think they're crazy."
    -- Rumble Fish.
--
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/