From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Marco Cipullo <cipullo@libero.it>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: In last setsid/tty locking changes...
Date: Fri, 07 Jan 2005 15:45:42 +0000 [thread overview]
Message-ID: <1105110088.17166.341.camel@localhost.localdomain> (raw)
In-Reply-To: <200501071437.02426.cipullo@libero.it>
On Gwe, 2005-01-07 at 13:37, Marco Cipullo wrote:
> In last setsid/tty locking changes:
> + down(&tty_sem);
> current->signal->tty = NULL;
> + up(&tty_sem);
>
> /* Block and flush all signals */
> sigfillset(&blocked);
>
> Sorry for the silly question, but why is needed a semaphore to write just one
> value without read/write nothing else?
Look at the tty init_dev code paths and it might make more sense. It
doesn't just say "protect this write" more importantly it says "don't do
this in parallel with tty setup"
prev parent reply other threads:[~2005-01-07 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 13:37 In last setsid/tty locking changes Marco Cipullo
2005-01-07 15:45 ` 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=1105110088.17166.341.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cipullo@libero.it \
--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