All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Sergey Lapin <slapin@ossfans.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ldisc problems with 2.6.32-2.6.37-rc2 (at least)
Date: Wed, 24 Nov 2010 20:43:11 +0100	[thread overview]
Message-ID: <4CED6ACF.9000402@suse.cz> (raw)
In-Reply-To: <20101124170326.GB7282@build.ihdev.net>

On 11/24/2010 06:03 PM, Sergey Lapin wrote:
>> Hi, I don't think you get similar backtraces in .37-rc2. Could you grab one?
> 
> Yeah, they are different definitely.

Weird, actually, it's the same warning. I cannot see how this can happen
though. The code looks like:
        tty_ldisc_close(tty, o_ldisc);

        /* Now set up the new line discipline. */
        tty_ldisc_assign(tty, new_ldisc);
        tty_set_termios_ldisc(tty, ldisc);

        retval = tty_ldisc_open(tty, new_ldisc);


Could you provide disassembly of tty_set_ldisc? E.g. by extracting it from:
objdump -d drivers/tty/tty_ldisc.o

thanks,
-- 
js
suse labs

  reply	other threads:[~2010-11-24 19:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 13:52 ldisc problems with 2.6.32-2.6.37-rc2 (at least) Sergey Lapin
2010-11-24 14:33 ` Jiri Slaby
2010-11-24 17:03   ` Sergey Lapin
2010-11-24 19:43     ` Jiri Slaby [this message]
2010-11-24 19:45       ` Jiri Slaby
2010-11-24 21:53         ` Sergey Lapin
2010-11-24 22:02           ` Jiri Slaby
2010-11-24 22:26             ` Sergey Lapin
2010-11-24 22:41               ` Jiri Slaby
2010-11-24 23:27                 ` [PATCH 1/2] TTY: ldisc, fix open flag handling Jiri Slaby
2010-11-29 21:50                   ` Greg KH
2010-11-29 22:41                     ` Jiri Slaby
2010-11-29 22:47                       ` Greg KH
2010-11-24 23:27                 ` [PATCH 2/2] NET: wan/x25, fix ldisc->open retval Jiri Slaby
2010-11-25 23:13                   ` Sergey Lapin
2010-11-24 22:03         ` ldisc problems with 2.6.32-2.6.37-rc2 (at least) Sergey Lapin

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=4CED6ACF.9000402@suse.cz \
    --to=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slapin@ossfans.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.