linux-kernel - Heads Up: tty locking changes

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: <20080129140936.0350d685@core>
Date:	Tue, 29 Jan 2008 14:09:36 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	linux-kernel@...r.kernel.org
Subject: Heads Up: tty locking changes

In the next few days I'll be submitting some further tty locking changes
to the kernel. Line discipline ->write and ->read methods will no longer
be covered by lock_kernel. For the moment tty->driver write methods won't
change (that is they will be either lock_kernel or in an IRQ but never
both). That is next on the hit list once the lock is driven out of the
tty ldisc layer.

If you have any out of tree ldiscs please be ready. If you maintain any
serial drivers still relying on lock_kernel for internal locking on the
read/write paths, now would be a good time to fix them before they break

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