From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Yi Wang <wang.yi59@zte.com.cn>,
kernel-janitors@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
Wen Yang <yellowriver2010@hotmail.com>,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr,
Cheng Shengyu <cheng.shengyu@zte.com.cn>,
Wen Yang <wen.yang99@zte.com.cn>
Subject: Re: [Cocci] [v4] coccinelle: semantic patch for missing put_device()
Date: Fri, 15 Feb 2019 09:19:54 +0100 [thread overview]
Message-ID: <8041ca90-5328-19ea-633e-e0b591c5723f@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1902150900270.2896@hadrien>
> The whole goal of the semantic patch is to ensure that put_device is
> called when needed.
Thanks for this clarification.
The software development goal seems to be clear to some degree.
> If the value is stored in a structure,
Will any further means become relevant for the discussed data processing?
> then someone else will likely take care of calling put_device later
> when the structure is destroyed.
Such a view is reasonable.
Are there any additional source code analysis and software development challenges
to consider for safer resource management?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-02-15 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201902151452197117145@zte.com.cn>
2019-02-15 6:55 ` [Cocci] [PATCH v4] coccinelle: semantic patch for missing put_device() Julia Lawall
2019-02-15 7:50 ` [Cocci] [v4] " Markus Elfring
2019-02-15 8:02 ` Julia Lawall
2019-02-15 8:19 ` Markus Elfring [this message]
[not found] <201902151422261425412@zte.com.cn>
2019-02-15 6:25 ` [Cocci] [PATCH v4] " Julia Lawall
2019-02-15 7:11 ` [Cocci] [v4] " Markus Elfring
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=8041ca90-5328-19ea-633e-e0b591c5723f@web.de \
--to=markus.elfring@web.de \
--cc=cheng.shengyu@zte.com.cn \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=wang.yi59@zte.com.cn \
--cc=wen.yang99@zte.com.cn \
--cc=yellowriver2010@hotmail.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;
as well as URLs for NNTP newsgroup(s).