From: Alan Cox <alan@redhat.com>
To: linux-ppp@vger.kernel.org
Subject: Re: possible bug on ppp_async
Date: Fri, 13 Jun 2008 19:38:16 +0000 [thread overview]
Message-ID: <20080613193816.GA2386@devserv.devel.redhat.com> (raw)
In-Reply-To: <6b53b1990806091123l74a06bebu34160ad08366d1a8@mail.gmail.com>
On Fri, Jun 13, 2008 at 03:01:52PM -0300, Gustavo Fernando Padovan wrote:
> > The problem seems the ioctl TCSETS, with the patch (and on kernel
> > 2.6.23) it returns immediately, and on kernel 2.6.24 (without the
> > patch) it goes to tty_mode_ioctl().
That is a fix for a long standing bug. It makes TCSETS/TCGETS work correctly
on a ppp session. So the bug is in your user space code somewhere it appears
and just happens to be triggered by fixing other bugs.
next prev parent reply other threads:[~2008-06-13 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 18:23 possible bug on ppp_async Gustavo Fernando Padovan
2008-06-09 18:52 ` Charlie Brady
2008-06-09 19:06 ` Gustavo Fernando Padovan
2008-06-09 21:03 ` Alan Cox
2008-06-11 20:55 ` Gustavo Fernando Padovan
2008-06-13 18:01 ` Gustavo Fernando Padovan
2008-06-13 18:19 ` Charlie Brady
2008-06-13 19:38 ` Alan Cox [this message]
2008-06-16 12:54 ` Gustavo Fernando Padovan
2008-06-16 17:09 ` Alan Cox
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=20080613193816.GA2386@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-ppp@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