| 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
| ||
|
Message-ID: <20120724230527.2135198e@bob.linux.org.uk> Date: Tue, 24 Jul 2012 23:05:27 +0100 From: Alan Cox <alan@...ux.intel.com> To: Ian Abbott <abbotti@....co.uk> Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Ian Abbott <ian.abbott@....co.uk>, lkml <linux-kernel@...r.kernel.org>, Greg KH <gregkh@...uxfoundation.org> Subject: Re: Oops after merge of tty-next On Mon, 23 Jul 2012 15:51:03 +0100 Ian Abbott <abbotti@....co.uk> wrote: > On 2012-07-21 23:41, Alan Cox wrote: > > On Fri, 20 Jul 2012 23:07:06 +0100 > > Ian Abbott <abbotti@....co.uk> wrote: > > > >> I'm getting an Oops in the linux-next tree today after the merge > >> of the remote-tracking branch 'tty/tty-next'. I bisected it down > >> to commit 36b3c070d2346c890d690d71f6eab02f8c511137 in > >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git : Ok Greg you can you leave that one in -next but not push it for 3.6. I need to go over this in some detail and figure out the remaining race, and worse yet how to fix it without the mess of existing locks turning it into something nasty. I think I understand what is needed but I don't want to be doing it as a mad panic for 3.6. On the bright side I think it explains the other tty lock splitting mysteries. 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/
Powered by blists - more mailing lists