From: Jamie Lokier <jamie@shareable.org>
To: Alan Cox <alan@linux.intel.com>
Cc: kvm@vger.kernel.org, borntraeger@de.ibm.com,
qemu-devel@nongnu.org, miltonm@bga.com,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
brueckner@linux.vnet.ibm.com, Amit Shah <amit.shah@redhat.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] Re: Extending virtio_console to support multiple ports
Date: Sat, 29 Aug 2009 02:15:17 +0100 [thread overview]
Message-ID: <20090829011517.GG8036@shareable.org> (raw)
In-Reply-To: <20090827100809.5f0aa0a7@linux.intel.com>
Alan Cox wrote:
> > - Then, are we certain that there's no case where the tty layer will
> > call us with some lock held or in an atomic context ? To be honest,
> > I've totally lost track of the locking rules in tty land lately so it
> > might well be ok, but something to verify.
>
> Some of the less well behaved line disciplines do this and always have
> done.
I had a backtrace in my kernel log recently which looked like that,
while doing PPP over Bluetooth RFCOMM. Resulted in AppArmor
complaining that it's hook was being called in irq context.
-- Jamie
next prev parent reply other threads:[~2009-08-29 1:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1251181044-3696-1-git-send-email-amit.shah@redhat.com>
[not found] ` <20090826112718.GA11117@amit-x200.redhat.com>
2009-08-26 15:45 ` Extending virtio_console to support multiple ports Amit Shah
2009-08-27 4:07 ` Benjamin Herrenschmidt
2009-08-27 6:51 ` [Qemu-devel] " Amit Shah
2009-08-27 9:08 ` Alan Cox
2009-08-27 9:27 ` Benjamin Herrenschmidt
2009-08-27 11:45 ` [PATCH] hvc_console: provide (un)locked version for hvc_resize() Hendrik Brueckner
2009-08-29 1:15 ` Jamie Lokier [this message]
2009-08-27 5:04 ` Extending virtio_console to support multiple ports Michael Ellerman
2009-08-27 6:52 ` Amit Shah
2009-08-27 14:13 ` Ryan Arnold
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=20090829011517.GG8036@shareable.org \
--to=jamie@shareable.org \
--cc=alan@linux.intel.com \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.org \
/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).