linux-kernel - Re: bug: isicom: kobject_add failed for ttyM0 with -EEXIST

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: <4586C882.6090906@gmail.com>
Date:	Mon, 18 Dec 2006 17:57:38 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	linux-kernel@...r.kernel.org
Subject: Re: bug: isicom: kobject_add failed for ttyM0 with -EEXIST

Ingo Molnar wrote:
> allyesconfig bzImage bootup produced 33 warning messages, of which the 
> first couple are attached below.

With which kernel? mxser had ttyM for a long time, it should be fixed in 2.6.20-rc1.


> --------------->
> Calling initcall 0xc0628d59: isicom_setup+0x0/0x315()
> kobject_add failed for ttyM0 with -EEXIST, don't try to register things with the same name in the same directory.
>  [<c0106273>] show_trace_log_lvl+0x34/0x4a
>  [<c01063a9>] show_trace+0x2c/0x2e
>  [<c01063d6>] dump_stack+0x2b/0x2d
>  [<c04f06a3>] kobject_add+0x15f/0x187
>  [<c06e3421>] class_device_add+0xb5/0x45c
>  [<c06e37e5>] class_device_register+0x1d/0x21
>  [<c06e3892>] class_device_create+0xa9/0xcc
>  [<c05f8a5c>] tty_register_device+0xe3/0xea
>  [<c05f97fa>] tty_register_driver+0x202/0x21e
>  [<c0628fa3>] isicom_setup+0x24a/0x315
>  [<c0100567>] init+0x178/0x451
>  [<c0105feb>] kernel_thread_helper+0x7/0x10
>  =======================
[...]

regards,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
-
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/