From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Greg KH <greg@kroah.com>,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [PATCH] add sysfs class support for vc devices [10/10]
Date: Fri, 16 Jan 2004 21:52:53 +0200 [thread overview]
Message-ID: <1074282773.23742.756.camel@nosferatu.lan> (raw)
In-Reply-To: <20040116111738.74636496.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
On Fri, 2004-01-16 at 21:17, Andrew Morton wrote:
> Martin Schlemmer <azarah@nosferatu.za.org> wrote:
> >
> > On Fri, 2004-01-16 at 06:13, Andrew Morton wrote:
> > > Greg KH <greg@kroah.com> wrote:
> > > >
> > > > This patch add sysfs support for vc char devices.
> > > >
> > > > Note, Andrew Morton has reported some very strange oopses with this
> > > > patch, that I can not reproduce at all. If anyone else also has
> > > > problems with this patch, please let me know.
> > >
> > > It seems to have magically healed itself :(
> > >
> > > Several people were hitting it. We shall see.
> >
> > Might it be due to the vt-locking-fixes patch?
> >
>
> No, I was able to reproduce the oops with just two of Greg's patches on
> bare 2.6.1-rcX.
>
> It was some refcounting problem in the tty layer. 100% deterministic, not
> a race.
No, I meant that fixed it. The locking patch was added _after_ you
removed the vc patch ...
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-16 19:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 20:40 [PATCH] sysfs class patch update [00/10] Greg KH
2004-01-15 20:41 ` [PATCH] add class_simple support [01/10] Greg KH
2004-01-15 20:41 ` [PATCH] add sysfs class support for input devices [02/10] Greg KH
2004-01-15 20:41 ` [PATCH] add class support for lp devices [03/10] Greg KH
2004-01-15 20:41 ` [PATCH] add sysfs class support for mem devices [04/10] Greg KH
2004-01-15 20:42 ` [PATCH] add sysfs class support for misc devices [05/10] Greg KH
2004-01-15 20:42 ` [PATCH] add sysfs class support for raw devices [06/10] Greg KH
2004-01-15 20:42 ` [PATCH] add sysfs class support for OSS sound devices [07/10] Greg KH
2004-01-15 20:43 ` [PATCH] add sysfs class support for ALSA sound devices [08/10] Greg KH
2004-01-15 20:43 ` [PATCH] clean up sysfs class support for tty devices [09/10] Greg KH
2004-01-15 20:43 ` [PATCH] add sysfs class support for vc devices [10/10] Greg KH
2004-01-16 4:13 ` Andrew Morton
2004-01-16 19:04 ` Martin Schlemmer
2004-01-16 19:17 ` Andrew Morton
2004-01-16 19:52 ` Martin Schlemmer [this message]
[not found] ` <yw1xu12v7d5t.fsf@kth.se>
2004-01-17 0:10 ` [PATCH] add sysfs class support for ALSA sound devices [08/10] Greg KH
2004-01-17 0:50 ` Måns Rullgård
2004-01-15 21:23 ` [PATCH] add sysfs class support for OSS sound devices [07/10] Prakash K. Cheemplavam
2004-01-15 21:32 ` Greg KH
2004-01-15 22:01 ` Prakash K. Cheemplavam
2004-01-20 1:58 ` [PATCH] add class_simple support [01/10] Rusty Russell
[not found] ` <yw1xoet5rktz.fsf@kth.se>
2004-01-15 22:56 ` [PATCH] sysfs class patch update [00/10] Greg KH
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=1074282773.23742.756.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®