From: Dan Carpenter <error27@gmail.com>
To: Alan Cox <alan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] tty: push the BKL down into the handlers a bit
Date: Fri, 20 Nov 2009 14:34:14 +0200 [thread overview]
Message-ID: <20091120123414.GA29012@bicker> (raw)
In-Reply-To: <20091118142404.3806.19238.stgit@localhost.localdomain>
On Wed, Nov 18, 2009 at 02:25:43PM +0000, Alan Cox wrote:
> Start trying to untangle the remaining BKL mess
>
> Signed-off-by: Alan "I must be out of my tree" Cox <alan@linux.intel.com>
> ---
>
> drivers/char/pty.c | 2 -
> drivers/char/tty_io.c | 140 ++++++++++++++++++++++++++--------------------
> drivers/char/tty_ldisc.c | 13 ++++
> include/linux/tty.h | 2 -
> 4 files changed, 94 insertions(+), 63 deletions(-)
>
1565 if (o_tty->termios != tty->driver->other->termios[idx]) {
1566 unlock_kernel();
1567 printk(KERN_DEBUG "tty_release_dev: other->termios[%d] "
1568 "not o_termios for (%s)\n",
1569 idx, tty->name);
1570 return 0;
1571 }
1572 if (o_tty->link != tty) {
We would need an unlock_kernel() here.
1573 printk(KERN_DEBUG "tty_release_dev: bad pty pointers\n");
1574 return 0;
1575 }
regards,
dan carpenter
next prev parent reply other threads:[~2009-11-20 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 14:23 [RFC PATCH 0/5] tty BKL pushdown Alan Cox
2009-11-18 14:25 ` [RFC PATCH 1/5] tty: push the BKL down into the handlers a bit Alan Cox
2009-11-20 12:34 ` Dan Carpenter [this message]
2009-11-18 14:26 ` [PATCH 2/5] tty: Push the lock down further into the ldisc code Alan Cox
2009-11-18 14:26 ` [PATCH 3/5] tty: Push the bkl down a bit in the hangup code Alan Cox
2009-11-18 14:26 ` [PATCH 4/5] tty: Move the leader test in disassociate Alan Cox
2009-11-18 14:26 ` [PATCH 5/5] tty: split the lock up a bit further Alan Cox
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=20091120123414.GA29012@bicker \
--to=error27@gmail.com \
--cc=alan@linux.intel.com \
--cc=linux-kernel@vger.kernel.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