From: Boaz Harrosh <bharrosh@panasas.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<samba-technical@lists.samba.org>,
Ganesha NFS List <nfs-ganesha-devel@lists.sourceforge.net>,
libc-alpha <libc-alpha@sourceware.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
"Carlos O'Donell" <carlos@redhat.com>,
Stefan Metzmacher <metze@samba.org>,
Andy Lutomirski <luto@amacapital.net>,
Frank Filz <ffilzlnx@mindspring.com>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH] locks: rename file-private locks to "open file description locks"
Date: Tue, 22 Apr 2014 18:05:13 +0300 [thread overview]
Message-ID: <53568529.2030103@panasas.com> (raw)
In-Reply-To: <20140422105520.7b09eda5@tlielax.poochiereds.net>
On 04/22/2014 05:55 PM, Jeff Layton wrote:
> On Tue, 22 Apr 2014 17:45:31 +0300
> Boaz Harrosh <openosd@gmail.com> wrote:
>
>
> There's a big difference between the descriptor and the description.
>
> The numerical value you get back from something like open() is a file
> descriptor.
Ha OK sorry I thought that was a file-handle I think in FBSD they
call it that. I guess file-handle is the NFS thing.
I guess the most common name for those is file-No, fn in
code
> The thing that that value points to internally in the
> kernel is the file description.
I did not know that and I completely interchanged these two.
In Kernel this is called plain "struct file" so I've never
seen this name used before.
OK Now it is clear
> It's very important that we do not
> conflate the two here as these locks are associated with the file
> description and not the file descriptor.
>
Sure you are right.
> The best way to illustrate this is the interaction with dup() -- see
> the LWN article on these for a complete overview.
>
I know the difference very well only I got the names mixed
Thanks
Boaz
next prev parent reply other threads:[~2014-04-22 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 12:23 [PATCH] locks: rename file-private locks to "open file description locks" Jeff Layton
2014-04-22 14:45 ` Boaz Harrosh
2014-04-22 14:55 ` Jeff Layton
2014-04-22 15:05 ` Boaz Harrosh [this message]
2014-04-22 15:00 ` Rich Felker
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=53568529.2030103@panasas.com \
--to=bharrosh@panasas.com \
--cc=carlos@redhat.com \
--cc=ffilzlnx@mindspring.com \
--cc=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=metze@samba.org \
--cc=mtk.manpages@gmail.com \
--cc=nfs-ganesha-devel@lists.sourceforge.net \
--cc=samba-technical@lists.samba.org \
--cc=tytso@mit.edu \
/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