From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Oleg Nesterov <oleg@tv-sign.ru>,
Prarit Bhargava <prarit@redhat.com>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH] tty: ->signal->tty locking
Date: Thu, 19 Oct 2006 14:09:55 +0100 [thread overview]
Message-ID: <1161263396.17335.42.camel@localhost.localdomain> (raw)
In-Reply-To: <1161260013.3036.92.camel@taijtu>
Ar Iau, 2006-10-19 am 14:13 +0200, ysgrifennodd Peter Zijlstra:
> Fix the locking of signal->tty.
>
> Use ->sighand->siglock to protect ->signal->tty; this lock is already used
> by most other members of ->signal/->sighand. And unless we are 'current' or
> the tasklist_lock is held we need ->siglock to access ->signal anyway.
Nice
Acked-by: Alan Cox <alan@redhat.com>
prev parent reply other threads:[~2006-10-19 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 12:13 [PATCH] tty: ->signal->tty locking Peter Zijlstra
2006-10-19 13:09 ` Alan Cox [this message]
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=1161263396.17335.42.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=prarit@redhat.com \
/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