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 23:02:46 +0100 [thread overview]
Message-ID: <4CED8B86.6070607@suse.cz> (raw)
In-Reply-To: <20101124215339.GA8691@build.ihdev.net>
On 11/24/2010 10:53 PM, Sergey Lapin wrote:
> Initially I run it, everything is ok.
> Then I run it and get error and backtrace.
> And if I run it again, everything is ok again, repeatedly. Probably some resources are properly
> set up in error condition, and not in normal condition.
>
> I use ARM machine for testing and x86, bug is architecture-independent.
>
> addr2lines:
> c01bc110 drivers/tty/tty_ldisc.c:499
Got it. Does this fixes the warning?
--- a/drivers/tty/tty_ldisc.c
+++ b/drivers/tty/tty_ldisc.c
@@ -454,6 +454,8 @@ static int tty_ldisc_open(struct tty_struct *tty,
struct tty_ldisc *ld)
/* BTM here locks versus a hangup event */
WARN_ON(!tty_locked());
ret = ld->ops->open(tty);
+ if (ret)
+ clear_bit(TTY_LDISC_OPEN, &tty->flags);
return ret;
}
return 0;
thanks,
--
js
suse labs
next prev parent reply other threads:[~2010-11-24 22:02 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
2010-11-24 19:45 ` Jiri Slaby
2010-11-24 21:53 ` Sergey Lapin
2010-11-24 22:02 ` Jiri Slaby [this message]
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=4CED8B86.6070607@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox