public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: karl malbrain <karl@petzent.com>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9 chrdev_open: serial_core: uart_open
Date: Fri, 15 Jul 2005 22:54:17 +0100	[thread overview]
Message-ID: <20050715225417.E23709@flint.arm.linux.org.uk> (raw)
In-Reply-To: <NDBBKFNEMLJBNHKPPFILGEAMCEAA.karl@petzent.com>; from karl@petzent.com on Fri, Jul 15, 2005 at 02:17:01PM -0700

On Fri, Jul 15, 2005 at 02:17:01PM -0700, karl malbrain wrote:
> > -----Original Message-----
> > From: Russell King
> > Sent: Friday, July 15, 2005 1:59 PM
> > To: karl malbrain
> > Cc: Linux-Kernel@Vger. Kernel. Org
> > Subject: Re: 2.6.9 chrdev_open: serial_core: uart_open
> >
> >
> > On Fri, Jul 15, 2005 at 01:52:15PM -0700, karl malbrain wrote:
> > > On my 2.6.9-11EL source it clearly shows the up(&tty_sem) after
> > the call to
> > > uart_open. Init_dev never touches tty_sem.
> >
> > In which case, I have to say...
> >
> > Congratulations!  You've found a bug with Red Hat's Enterprise Linux
> > kernel!  Go straight to Red Hat's bugzilla!  Do not collect 200$.  Do
> > not pass go.
> >
> > Seriously though, this bug is not present in mainline kernels, so I
> > can't resolve this issue for you.  Mainline kernels appear to work
> > properly.
> 
> Could tty_io.c be all that changed by a small set of red-hat patches to
> 2.6.9?  Why would they need to go in there to make so many changes in the
> first place?  Which 2.6 release changed tty_io.c's use of tty_sem so
> heavily?

These are questions to ask of Red Hat, and can only be answered by
their representatives.

Thanks anyway, and I'm sorry that this hasn't been resolved given
the amount of time put into it by both of us.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-07-15 21:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.61.0507130850110.18969@chaos.analogic.com>
2005-07-13 17:53 ` 2.6.9: serial_core: uart_open karl malbrain
2005-07-14  8:26   ` Russell King
2005-07-14 17:16     ` karl malbrain
2005-07-14 18:57       ` Russell King
2005-07-14 19:30         ` karl malbrain
2005-07-14 22:35         ` karl malbrain
2005-07-15  7:28           ` Russell King
2005-07-15 16:02             ` karl malbrain
2005-07-15 20:32               ` Russell King
2005-07-15 20:48                 ` karl malbrain
2005-07-15 16:20             ` karl malbrain
2005-07-14 23:50         ` 2.6.9 chrdev_open: " karl malbrain
2005-07-15  7:22           ` Russell King
2005-07-15 20:11             ` karl malbrain
2005-07-15 20:30               ` Russell King
2005-07-15 20:52                 ` karl malbrain
2005-07-15 20:58                   ` Russell King
2005-07-15 21:17                     ` karl malbrain
2005-07-15 21:54                       ` Russell King [this message]
2005-07-15 22:02                         ` karl malbrain
2005-07-16  0:18                           ` Alan Cox
2005-07-26 20:45                         ` karl malbrain
2005-07-16  0:12               ` Alan Cox
2005-07-16 22:27                 ` Matthias Urlichs

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=20050715225417.E23709@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=karl@petzent.com \
    --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