From: Greg KH <gregkh@linuxfoundation.org>
To: "Zhang, Qiang" <Qiang.Zhang@windriver.com>
Cc: "balbi@kernel.org" <balbi@kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 回复: 回复: [PATCH v2] usb: gadget: function: printer: fix use-after-free in __lock_acquire
Date: Thu, 18 Jun 2020 10:28:18 +0200 [thread overview]
Message-ID: <20200618082818.GA1058534@kroah.com> (raw)
In-Reply-To: <DM5PR11MB20589EB35828F823826FF4B3FF830@DM5PR11MB2058.namprd11.prod.outlook.com>
On Wed, Jun 10, 2020 at 04:58:44AM +0000, Zhang, Qiang wrote:
> cdev object reference count and "struct printer_dev" object
> reference count(kref), This two reference counts do not conflict. in
> file usb-skeleton.c also used a similar method， "struct usb_skel"
> contains kref members.
I do not understand what you are referring to here, sorry.
greg k-h
prev parent reply other threads:[~2020-06-18 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 7:16 [PATCH v2] usb: gadget: function: printer: fix use-after-free in __lock_acquire qiang.zhang
2020-06-08 7:33 ` Greg KH
2020-06-09 9:35 ` 回复: " Zhang, Qiang
2020-06-09 9:48 ` Greg KH
2020-06-10 4:58 ` 回复: " Zhang, Qiang
2020-06-18 8:28 ` Greg KH [this message]
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=20200618082818.GA1058534@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Qiang.Zhang@windriver.com \
--cc=balbi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 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).