From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: 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: Fri, 26 Oct 2012 13:37:54 +0000 [thread overview]
Message-ID: <20121026143754.50277bd8@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <50899507.1040900@oracle.com>
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
Alan
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: 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: Fri, 26 Oct 2012 14:37:54 +0100 [thread overview]
Message-ID: <20121026143754.50277bd8@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <50899507.1040900@oracle.com>
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
Alan
next prev parent reply other threads:[~2012-10-26 13:37 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 19:37 tty, vt: lockdep warnings Sasha Levin
2012-10-26 13:37 ` Alan Cox [this message]
2012-10-26 13:37 ` Alan Cox
2012-11-05 17:26 ` Sasha Levin
2012-11-05 17:26 ` Sasha Levin
2012-11-05 17:59 ` Alan Cox
2012-11-05 17:59 ` Alan Cox
2012-11-05 18:00 ` Sasha Levin
2012-11-05 18:00 ` Sasha Levin
2012-11-05 19:17 ` Hugh Dickins
2012-11-05 19:17 ` Hugh Dickins
2012-11-05 20:15 ` Alan Cox
2012-11-05 20:15 ` Alan Cox
2012-11-05 20:34 ` Hugh Dickins
2012-11-05 20:34 ` Hugh Dickins
2012-11-06 16:11 ` Alan Cox
2012-11-06 16:11 ` Alan Cox
2012-11-06 16:42 ` Dave Jones
2012-11-06 16:42 ` Dave Jones
2012-11-06 17:38 ` Alan Cox
2012-11-06 17:38 ` Alan Cox
2012-11-07 13:47 ` Sasha Levin
2012-11-07 13:47 ` Sasha Levin
2012-11-07 15:57 ` Alan Cox
2012-11-07 16:02 ` Alan Cox
2012-11-07 16:15 ` Bjørn Mork
2012-11-07 16:15 ` Bjørn Mork
2012-11-07 16:56 ` Alan Cox
2012-11-07 17:01 ` Alan Cox
2012-11-08 14:34 ` tty, vt: lockdep warnings (Patch v3) Alan Cox
2012-11-08 14:34 ` Alan Cox
2012-11-09 19:34 ` Hugh Dickins
2012-11-09 19:34 ` Hugh Dickins
2012-11-09 19:42 ` Sasha Levin
2012-11-09 19:42 ` Sasha Levin
2012-11-13 16:24 ` Sasha Levin
2012-11-13 16:24 ` Sasha Levin
2012-11-07 4:29 ` tty, vt: lockdep warnings Hugh Dickins
2012-11-07 4:29 ` Hugh Dickins
2012-11-07 6:26 ` 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=20121026143754.50277bd8@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.