From: Sergey Vlasov <vsu@altlinux.ru>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Patch] 2.4.28-pre3 tty/ldisc fixes
Date: Sat, 30 Oct 2004 23:19:55 +0400 [thread overview]
Message-ID: <20041030191955.GA2310@sirius.home> (raw)
In-Reply-To: <Pine.LNX.4.44.0410291426240.13340-200000@dhcp83-105.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]
On Fri, Oct 29, 2004 at 02:29:43PM -0400, Jason Baron wrote:
>
> On Thu, 28 Oct 2004, Sergey Vlasov wrote:
>
> > Here the comment is unclosed; is this intentional? Simply closing it
> > at the same line gives a kernel which cannot complete the system boot
> > process: it prints "init_dev but no ldisc", and then init hangs in
> > uninterruptible sleep with this backtrace:
> >
> > Adhoc c0188ab7 <tty_ldisc_ref_wait+47/80>
> > Adhoc c0199c30 <con_write+0/30>
> > Adhoc c0189648 <tty_write+118/270>
> > Adhoc c0139728 <chrdev_open+38/50>
> > Adhoc c01386e3 <dentry_open+e3/190>
> > Adhoc c0138f16 <sys_write+96/f0>
> > Adhoc c01385eb <filp_open+4b/60>
> > Adhoc c014246f <getname+5f/a0>
> > Adhoc c0138937 <sys_open+57/80>
> >
>
> Here's an updated 2.4 tty patch. I'm not sure if the updated patch would
> fix the above issue, but it has a lot of changes so it might be worth a
> try.
This looks better - at least the system boots without hang or oops ;)
However, drivers/net/wan/pc300_tty.c does not compile:
> @@ -699,12 +693,19 @@ static void cpc_tty_rx_task(void * data)
> cpc_tty = &cpc_tty_area[port];
>
> if ((buf=cpc_tty->buf_rx.first) != 0) {
> -
> - if (cpc_tty->tty && (cpc_tty->tty->ldisc.receive_buf)) {
> - CPC_TTY_DBG("%s: call line disc. receive_buf\n",cpc_tty->name);
> - cpc_tty->tty->ldisc.receive_buf(cpc_tty->tty, (const unsigned char *)buf->data,
> - &flags, buf->size);
> - }
> +
> + if(cpc_tty->tty)
> + {
> + ld = tty_ldisc_ref(cpc_tty);
struct tty_ldisc *ld = tty_ldisc_ref(cpc_tty->tty);
> + if(ld)
> + {
> + if (ld->receive_buf)) {
if (ld->receive_buf) {
> + CPC_TTY_DBG("%s: call line disc. receive_buf\n",cpc_tty->name);
> + ld->receive_buf(cpc_tty->tty, (char *)(buf->data), &flags, buf->size);
> + }
> + tty_ldisc_deref(ld);
> + }
> + }
> cpc_tty->buf_rx.first = cpc_tty->buf_rx.first->next;
> kfree((unsigned char *)buf);
> buf = cpc_tty->buf_rx.first;
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-30 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 17:49 [Patch] 2.4.28-pre3 tty/ldisc fixes Jason Baron
2004-10-28 18:35 ` Sergey Vlasov
2004-10-28 18:42 ` Jason Baron
[not found] ` <Pine.LNX.4.44.0410291426240.13340-200000@dhcp83-105.boston.redhat.com>
2004-10-30 19:19 ` Sergey Vlasov [this message]
2004-10-31 9:53 ` Krzysztof Taraszka
2004-11-02 15:02 ` Jason Baron
2004-11-07 20:06 ` Sergey Vlasov
2004-11-07 20:10 ` [PATCH] Update termios to use per tty semaphore (backport from 2.6.x) Sergey Vlasov
2004-11-07 20:13 ` [PATCH] Add back lost call to tty->driver.set_termios Sergey Vlasov
2004-10-31 17:18 ` [Patch] 2.4.28-pre3 tty/ldisc fixes Sergey Vlasov
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=20041030191955.GA2310@sirius.home \
--to=vsu@altlinux.ru \
--cc=jbaron@redhat.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