linux-kernel - Re: Oops after merge of tty-next

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

Message-ID: <20120721234145.354e6ee9@pyramind.ukuu.org.uk>
Date:	Sat, 21 Jul 2012 23:41:45 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Ian Abbott <abbotti@....co.uk>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Alan Cox <alan@...ux.intel.com>,
	Greg KH <gregkh@...uxfoundation.org>
Subject: Re: Oops after merge of tty-next

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 :
> 
>    tty: Move the handling of the tty release logic

Ok that's not improbable, I thought I had them all nailed.

> Sorry, I don't have a copy of the Oops right now, but it's failing 
> somewhere in tty_open() or check_tty_count() during system boot, 
> probably when getty opens one of the vc tty devices.

That would be more surprising as its a path I tested a lot but strange
things occur. What may also be very important is to know what distro you
are using.

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/