From: Paul Fulghum <paulkf@microgate.com>
To: Greg KH <greg@kroah.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-stable <stable@kernel.org>
Subject: Re: [stable] Success: tty_io flush_to_ldisc() error message triggered
Date: Tue, 25 Jul 2006 14:12:28 -0500 [thread overview]
Message-ID: <44C66D1C.7010903@microgate.com> (raw)
In-Reply-To: <20060725184158.GH9021@kroah.com>
Greg KH wrote:
> On Sat, Jul 22, 2006 at 11:41:44AM -0500, Paul Fulghum wrote:
>
>>Chuck Ebbert wrote:
>>
>>>The cleaner fix looks more intrusive, though.
>>>
>>>Is this simpler change (what I'm running but without the warning
>>>messages) the preferred fix for -stable?
>>
>>It fixes the problem.
>
>
> So do you feel this patch should be added to the -stable kernel tree?
No. Now that I think about it, adding that extra
macro is just wrong even if temporary.
The real fix is equally simple, but in 2.6.18-rc
it is intertwined with other more intrusive changes.
Let me make a new separate patch that does things
the right way, which is simply removing the list
head while processing the list so two instances
to not trip over each other. I would have done so
earlier, but I've been insanely busy with multiple
work related deadlines (lame excuse I know).
I should post something tomorrow afternoon.
--
Paul Fulghum
Microgate Systems, Ltd.
next prev parent reply other threads:[~2006-07-25 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 16:07 Success: tty_io flush_to_ldisc() error message triggered Chuck Ebbert
2006-07-22 16:41 ` Paul Fulghum
2006-07-25 18:41 ` [stable] " Greg KH
2006-07-25 19:12 ` Paul Fulghum [this message]
2006-07-26 7:16 ` Greg KH
[not found] ` <1153941029.6903.5.camel@amdx2.microgate.com>
2006-07-28 13:53 ` [PATCH]: tty buffering limit Alan Cox
2006-07-28 15:36 ` Paul Fulghum
-- strict thread matches above, loose matches on Subject: below --
2006-07-25 19:19 [stable] Success: tty_io flush_to_ldisc() error message triggered Chuck Ebbert
2006-07-25 20:16 ` Paul Fulghum
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=44C66D1C.7010903@microgate.com \
--to=paulkf@microgate.com \
--cc=76306.1226@compuserve.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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