From: Markus Elfring <Markus.Elfring@web.de>
To: Xu Wang <vulab@iscas.ac.cn>, linux-i2c@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 2/2] i2c: Fix a potential use after free
Date: Sat, 28 Dec 2019 13:50:22 +0100 [thread overview]
Message-ID: <81b35c80-74c2-e14e-4947-f23ec6197b73@web.de> (raw)
In-Reply-To: <1577439272-10362-1-git-send-email-vulab@iscas.ac.cn>
> Free the adap structure only after we are done using it.
This information can be reasonable.
> This patch just moves the put_device() down a bit to avoid the
> use after free.
I suggest to reconsider such a change because a device reference count
should eventually be decremented before decrementing the reference count
for the module which is managed by this programming interface.
Would you like to clarify the dependencies for such an use case any more?
Regards,
Markus
next prev parent reply other threads:[~2019-12-28 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 9:34 [PATCH 2/2] i2c: Fix a potential use after free Xu Wang
2019-12-28 12:50 ` Markus Elfring [this message]
2020-03-22 15:56 ` Wolfram Sang
2022-06-16 21:00 ` Wolfram Sang
2022-07-26 21:13 ` Wolfram Sang
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=81b35c80-74c2-e14e-4947-f23ec6197b73@web.de \
--to=markus.elfring@web.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
--cc=wsa@the-dreams.de \
/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).