linux-kernel - Re: ldisc problems with 2.6.32-2.6.37-rc2 (at least)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CED6ACF.9000402@suse.cz>
Date:	Wed, 24 Nov 2010 20:43:11 +0100
From:	Jiri Slaby <jslaby@...e.cz>
To:	Sergey Lapin <slapin@...fans.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: ldisc problems with 2.6.32-2.6.37-rc2 (at least)

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/