From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: k8 s <uint32@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Doubt Regarding Multithreading and Device Driver
Date: Wed, 27 Apr 2005 16:46:43 +0100 [thread overview]
Message-ID: <20050427154643.GX13052@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <699a19ea05042708305fb7194b@mail.gmail.com>
On Wed, Apr 27, 2005 at 09:00:58PM +0530, k8 s wrote:
> But i am sharing something in file->private_data which is a private
> variable to the process(that is passed to the device driver
> functions). Isn't it?
It is not. It is private to struct file. Not to process. And any number
of things (starting with fork()) will give several processes references to
the same struct file. As soon as it had returned from ->open(), it should
be considered externally visible and potentially shared until ->release()
is called.
next prev parent reply other threads:[~2005-04-27 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 15:05 k8 s
2005-04-27 15:10 ` Max Kellermann
2005-04-27 15:30 ` k8 s
2005-04-27 15:41 ` Paulo Marques
2005-04-27 15:46 ` Al Viro [this message]
2005-04-27 15:34 ` Richard B. Johnson
2005-04-27 15:34 ` Jonathan Corbet
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=20050427154643.GX13052@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=uint32@gmail.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
all inboxes | Powered by JetHome®