linux-kernel - [PATCH -mm 0/2] Redo write_trylock

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: <Pine.LNX.4.64.0705110023020.30531@cselinux1.cse.iitk.ac.in>
Date:	Fri, 11 May 2007 00:29:25 +0530 (IST)
From:	Satyam Sharma <ssatyam@....iitk.ac.in>
To:	linux-kernel@...r.kernel.org
cc:	akpm@...ux-foundation.org, mingo@...e.hu, sripathik@...ibm.com
Subject: [PATCH -mm 0/2] Redo write_trylock_irqsave() in -mm

-mm recently added a write_trylock_irqsave() implementation. We can do
a better implementation than that, so we're able to:

1. Have a slightly faster implementation
2. Have a far lesser invasive patch (add fewer lines, touch fewer files)
3. Be consistent in style with the spin_trylock_irqsave() of mainline and -mm

(http://lkml.org/lkml/2007/5/9/575)

> For the sake of completeness of the API, we could also add a
> read_trylock_irqsave, but I'd be against the _irq variants (or should
> we call them hazards) that don't save / restore.

[PATCH -mm 1/2] Kills the previous implementation of write_trylock_irqsave()

[PATCH -mm 2/2] Reintroduces the new implementation of write_trylock_irqsave()

Signed-off-by: Satyam Sharma <ssatyam@....iitk.ac.in>

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