linux-kernel - Re: [PATCH] tty restore locked ioctl file op

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

Date:	Sat, 09 Jun 2007 15:52:17 -0600
From:	Paul Fulghum <paulkf@...rogate.com>
To:	Björn Steinbrink <B.Steinbrink@....de>,
	Paul Fulghum <paulkf@...rogate.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Arnd Bergmann <arnd@...db.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Nicolas Mailhot <nicolas.mailhot@...oste.net>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	"bugme-daemon@...nel-bugs.osdl.org" 
	<bugme-daemon@...zilla.kernel.org>, linux-kernel@...r.kernel.org,
	Mel Gorman <mel@....ul.ie>,
	Christoph Lameter <clameter@....com>
Subject: Re: [PATCH] tty restore locked ioctl file op

Björn Steinbrink wrote:
> Sorry for the delay, your mails didn't make it into my inbox, and I
> usually just mark threads on which I'm Cc'ed as read in my lkml mailbox,
> thus I didn't notice it earlier. Any traces of the lost mails on your
> side?

No clues on this end.

> The patch works as expected, no Oops in sight. Regarding the
> reproducability, it might be that it was easier to trigger on rc1. When
> I retried today with rc4, I only got 2 Oopses in a minute, while the
> first test had spitten out about 20 Oopses in 10 seconds (not sure if I
> really had rc1 running back then, though).

I'm sure it's very timing dependent.
I'm confident with this fix.

Thanks for your help.

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