From: Randy Dunlap <rdunlap@infradead.org>
To: Anup Parikh <parikhanupk.foss@gmail.com>
Cc: skhan@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Doc fix for dget_dlock
Date: Thu, 11 Aug 2022 11:33:04 -0700 [thread overview]
Message-ID: <e055ac0c-312d-78cd-dcc9-7c2e80ea3d3d@infradead.org> (raw)
In-Reply-To: <CAH6MFJGuHptQ8peBb8myLR8fgtLtAXwvUePcs7dbzYszF9Yyyw@mail.gmail.com>
Hi--
On 8/11/22 07:48, Anup Parikh wrote:
> Hello Mr. Randy Dunlap,
>
> I checked include/linux/dcache.h (dget() and dget_dlock()), include/linux/lockref.h and linux/lib/lockref.c.
> My current knowledge is limited but I think:
> 1) dget_dlock() directly increments the count variable without any atomicity guards.
> 2) dget() does the same but with atomicity guarantee - even across multiple-cores on a multi-core system (according to https://stackoverflow.com/questions/36964478/understanding-synchronization-with-multiple-processors <https://stackoverflow.com/questions/36964478/understanding-synchronization-with-multiple-processors> and code in linux/lib/lockref.c).
>
> Please let me know if I should write the corresponding documentation and send a new patch.
Yes, please.
Thanks.
> Thanks and Regards,
> Anup K Parikh.
>
>
> On Tue, Aug 9, 2022 at 11:58 PM Randy Dunlap <rdunlap@infradead.org <mailto:rdunlap@infradead.org>> wrote:
>
> Hi--
>
> On 8/5/22 09:39, Anup K Parikh wrote:
> > Removes the warning for dget_dlock in include/linux/dcache.h and
> > enables generation of its API documentation
> >
> > Signed-off-by: Anup K Parikh <parikhanupk.foss@gmail.com <mailto:parikhanupk.foss@gmail.com>>
> > ---
> > include/linux/dcache.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/linux/dcache.h b/include/linux/dcache.h
> > index f5bba5148..ce0b36f72 100644
> > --- a/include/linux/dcache.h
> > +++ b/include/linux/dcache.h
> > @@ -297,7 +297,7 @@ extern char *dentry_path(const struct dentry *, char *, int);
> > /* Allocation counts.. */
> >
> > /**
> > - * dget, dget_dlock - get a reference to a dentry
> > + * dget_dlock - get a reference to a dentry
> > * @dentry: dentry to get a reference to
> > *
> > * Given a dentry or %NULL pointer increment the reference count
>
> Someone was trying to document both dget() and get_dlock() with the same
> kernel-doc comment block.
> I suppose that you could duplicate the comments for dget() also.
>
> It would be nice to know the difference(s) in the functions as well.
>
> thanks.
> --
> ~Randy
>
--
~Randy
next prev parent reply other threads:[~2022-08-11 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 16:39 Anup K Parikh
2022-08-09 15:29 ` Shuah Khan
2022-08-09 18:28 ` Randy Dunlap
[not found] ` <CAH6MFJGuHptQ8peBb8myLR8fgtLtAXwvUePcs7dbzYszF9Yyyw@mail.gmail.com>
2022-08-11 18:33 ` Randy Dunlap [this message]
2022-08-11 18:35 ` Randy Dunlap
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=e055ac0c-312d-78cd-dcc9-7c2e80ea3d3d@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parikhanupk.foss@gmail.com \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®