From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Fw: [Bugme-new] [Bug 7952] New: slattach only works every other time Date: Tue, 6 Feb 2007 13:57:54 -0800 Message-ID: <20070206135754.0a0415b9.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Stephen Hemminger , mfuzzey@mailclub.net, "bugme-daemon@kernel-bugs.osdl.org" To: netdev@vger.kernel.org Return-path: Received: from smtp.osdl.org ([65.172.181.24]:52656 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965465AbXBFV6Y (ORCPT ); Tue, 6 Feb 2007 16:58:24 -0500 Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Begin forwarded message: Date: Tue, 6 Feb 2007 13:01:55 -0800 From: bugme-daemon@bugzilla.kernel.org To: bugme-new@lists.osdl.org Subject: [Bugme-new] [Bug 7952] New: slattach only works every other time http://bugzilla.kernel.org/show_bug.cgi?id=7952 Summary: slattach only works every other time Kernel Version: 2.6.18 Status: NEW Severity: normal Owner: acme@conectiva.com.br Submitter: mfuzzey@mailclub.net Most recent kernel where this bug did *NOT* occur:2.6.16 Distribution:Debian Etch Hardware Environment: x86 with serial port (including qemu) Software Environment: slattach Problem Description: First time slattach is run to set up a SLIP line all is ok. If slattach process is then killed and restarted it fails with message: SLIP_set_disc(1): File exists Problem still occurs in 2.6.20rc6 kernel dmesg shows: object_add failed for sl0 with -EEXIST, don't try to register things with the same name in the same directory. [] kobject_add+0x147/0x16d [] class_device_add+0x9d/0x3b3 [] register_netdevice+0x21a/0x2d0 [] slip_open+0x3a1/0x4e2 [slip] [] tty_ioctl+0x922/0xbac [] default_wake_function+0x0/0xc [] n_tty_open+0x0/0x88 [] n_tty_close+0x0/0x25 [] n_tty_flush_buffer+0x0/0x3b [] n_tty_chars_in_buffer+0x0/0x5b [] read_chan+0x0/0x551 [] write_chan+0x0/0x294 [] n_tty_ioctl+0x0/0x40d [] n_tty_set_termios+0x0/0x1cc [] normal_poll+0x0/0x119 [] n_tty_receive_buf+0x0/0xcf9 [] n_tty_write_wakeup+0x0/0x27 [] parport_pc_interrupt+0x1a/0x42 [parport_pc] [] handle_IRQ_event+0x23/0x49 [] __do_IRQ+0xb3/0xe8 [] __do_IRQ+0xd7/0xe8 [] hrtimer_run_queues+0xcf/0x157 [] do_ioctl+0x47/0x5d [] vfs_ioctl+0x24a/0x25c [] tasklet_action+0x55/0xaf [] sys_ioctl+0x48/0x5f [] sysenter_past_esp+0x56/0x79 Steps to reproduce: (requires a serial port but nothing needs to be attached to it): # slattach -L -vd -p slip -s 115200 /dev/ttyS0 slattach: tty_open: looking for lock slattach: tty_open: trying to open /dev/ttyS0 slattach: tty_open: /dev/ttyS0 (fd=3) slattach: tty_set_speed: 115200 slattach: tty_set_databits: 8 slattach: tty_set_stopbits: 1 slattach: tty_set_parity: N slip started on /dev/ttyS0 interface sl0 Above is OK, now kill process with CTRL-C slattach: tty_set_speed: 0 # slattach -L -vd -p slip -s 115200 /dev/ttyS0 slattach: tty_open: looking for lock slattach: tty_open: trying to open /dev/ttyS0 slattach: tty_open: /dev/ttyS0 (fd=3) slattach: tty_set_speed: 115200 slattach: tty_set_databits: 8 slattach: tty_set_stopbits: 1 slattach: tty_set_parity: N SLIP_set_disc(1): File exists # dmesg Gives trace shown above I believe this is called by this changeset : http://www2.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.17.y.git;a=commit;h=b17a7c179dd3ce7d04373fddf660eda21efc9db9 Regards, Martin ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.