From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>,
linux-fbdev@vger.kernel.org, florianSchandinat@gmx.de
Subject: Re: tty, vt: lockdep warnings
Date: Mon, 05 Nov 2012 17:59:37 +0000 [thread overview]
Message-ID: <20121105175937.26f31d2a@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CA+1xoqdEesjh1EZvR_r7Hn0GUc7741EDWn59qagngcxg4=9bjQ@mail.gmail.com>
On Mon, 5 Nov 2012 12:26:43 -0500
Sasha Levin <levinsasha928@gmail.com> wrote:
> Ping? Should I bisect it?
>
> On Fri, Oct 26, 2012 at 9:37 AM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > On Thu, 25 Oct 2012 15:37:43 -0400
> > Sasha Levin <sasha.levin@oracle.com> wrote:
> >
> >> Hi all,
> >>
> >> While fuzzing with trinity inside a KVM tools (lkvm) guest running latest -next kernel,
> >> I've stumbled on the following spew:
> >
> > Looks real enough but its not a tty/vt layer spew. This is all coming out
> > of the core framebuffer code which doesn't seem to be able to decide what
> > the locking rules at the invocation of fb_notifier_call_chain are.
> >
> > It might need some console layer tweaking to provide 'register console
> > and I already hold the locks' or similar but that notifier needs some
> > kind of sanity applying as well.
> >
> > Cc'ing the fbdev folks
I've cc'd the framebuffer folks. I can see why its occurring but I have
no idea how they intend to fix it and I've not seen any replies.
Sorry but I've got enough other things on my plate right now without
trying to deal with the locking brain damage that the fbdev layer is.
As far as I can tell the actual bug proper is years old.
Alan
next prev parent reply other threads:[~2012-11-05 17:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50899507.1040900@oracle.com>
2012-10-26 13:37 ` tty, vt: lockdep warnings Alan Cox
2012-11-05 17:26 ` Sasha Levin
2012-11-05 17:59 ` Alan Cox [this message]
2012-11-05 18:00 ` Sasha Levin
2012-11-05 19:17 ` Hugh Dickins
2012-11-05 20:15 ` Alan Cox
2012-11-05 20:34 ` Hugh Dickins
2012-11-06 16:11 ` Alan Cox
2012-11-06 16:42 ` Dave Jones
2012-11-06 17:38 ` Alan Cox
2012-11-07 13:47 ` Sasha Levin
2012-11-07 15:57 ` Alan Cox
2012-11-07 16:15 ` Bjørn Mork
2012-11-07 16:56 ` Alan Cox
2012-11-08 14:34 ` tty, vt: lockdep warnings (Patch v3) Alan Cox
2012-11-09 19:34 ` Hugh Dickins
2012-11-09 19:42 ` Sasha Levin
2012-11-13 16:24 ` Sasha Levin
2012-11-07 4:29 ` tty, vt: lockdep warnings Hugh Dickins
2012-11-07 6:26 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121105175937.26f31d2a@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=florianSchandinat@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=levinsasha928@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).