From: Lee Revell <rlrevell@joe-job.com>
To: Stuart MacDonald <stuartm@connecttech.com>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: Proper use of daemonize()?
Date: Wed, 06 Oct 2004 11:55:14 -0400 [thread overview]
Message-ID: <1097078113.1903.61.camel@krustophenia.net> (raw)
In-Reply-To: <030601c4abb7$af573770$294b82ce@stuartm>
On Wed, 2004-10-06 at 11:18, Stuart MacDonald wrote:
> I've been looking at the kernel threads that use daemonize() and have
> some questions about the proper use of this call:
>
> 1: Some threads use the lock_kernel() calls around the daemonize()
> call. Is this necessary?
It's only necessary if you can't be bothered to do proper locking.
Probably that code is old and someone did not have time to implement
correct locking to make it work on SMP so just threw lock/unlock kernel
around it.
> I thought the BKL was phasing out.
>
Well, it's not going to phase itself out ;-) But, patches that
introduce new uses of the BKL will almost certainly go to /dev/null.
Lee
next prev parent reply other threads:[~2004-10-06 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 15:18 Proper use of daemonize()? Stuart MacDonald
2004-10-06 15:55 ` Lee Revell [this message]
2004-10-06 16:51 ` Chris Wright
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=1097078113.1903.61.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stuartm@connecttech.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