public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rick Warner <rick@microway.com>
To: linux-kernel@vger.kernel.org
Subject: serial port regression caused by "Char: tty_ioctl, use wait_event_interruptible_timeout" patch
Date: Tue, 5 Feb 2008 14:02:26 -0500	[thread overview]
Message-ID: <200802051402.26816.rick@microway.com> (raw)

Hello all,

My company uses a proprietary hardware monitoring solution that utilizes 
communication over the serial port.  A RS232-RS485 converter is plugged into 
the serial port of the master of a cluster, and cat5 cables are daisy chained 
between the cards to handle out of band hardware monitoring.  The cards 
themselves speak RS485.  We have been using the same software to read the 
data from the serial port since the 2.4 kernel days.   As of 2.6.23, the 
software no longer works.

I narrowed down the problem doing a binary search on git snapshots between .22 
and .23, and found the breakage between git6 and git7.  Further isolating it 
found the patch mentioned in the subject to be the cause.  I reversed the 
patch in the .23 source and it now works properly.

Should the code be reverted back as I did, or is there something I should 
change in our userspace code that reads from the serial port to correct it 
instead?

Thanks,
Rick

-- 
Richard Warner
Lead Systems Integrator
Microway, Inc
(508)732-5517

             reply	other threads:[~2008-02-05 19:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 19:02 Rick Warner [this message]
2008-02-05 20:18 ` serial port regression caused by "Char: tty_ioctl, use wait_event_interruptible_timeout" patch Paul Fulghum
2008-02-05 20:53   ` Paul Fulghum
2008-02-05 21:32     ` Rick Warner
2008-02-05 21:37       ` Paul Fulghum
2008-02-05 21:59         ` Jiri Slaby
2008-02-05 22:27           ` Paul Fulghum
2008-02-05 22:33             ` Jiri Slaby

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=200802051402.26816.rick@microway.com \
    --to=rick@microway.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