From: Steve French <smfrench@austin.rr.com>
To: linux-kernel@vger.kernel.org
Subject: ->pid in filesystem code
Date: Fri, 29 Aug 2003 02:05:57 -0500 [thread overview]
Message-ID: <3F4EFB55.8090300@austin.rr.com> (raw)
Yes the cifs vfs code was using current->pid in multiple places and in
about five of the places the meaning
really was process id, and thus presumably better to change this to
current->tgid. I have made the change
from pid to tgid for those places in the bk tree for the cifs vfs
(http://cifs.bkbits.net/linux-2.5cifs) and will try them out.
The locking tests needed to be rerun anyway.
next reply other threads:[~2003-08-29 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 7:05 Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 19:12 ->pid in filesystem code Ulrich Drepper
2003-08-29 8:17 ` viro
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=3F4EFB55.8090300@austin.rr.com \
--to=smfrench@austin.rr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.