> -----Original Message----- > From: Russell King > Sent: Friday, July 15, 2005 1:59 PM > To: karl malbrain > Cc: [EMAIL PROTECTED] 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? This conflict between main-line/redhat looks much worse than the unix sysV r4.0 divergence after 3.2. Ouch. Thanks for your help, though. karl m - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
