From: Alan Stern <stern@rowland.harvard.edu>
To: Johan Hovold <johan@kernel.org>
Cc: Oliver Neukum <oneukum@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: drop misleading usb_set_intfdata() kernel doc
Date: Mon, 12 Dec 2022 11:39:15 -0500 [thread overview]
Message-ID: <Y5dZM68riR/EGn8W@rowland.harvard.edu> (raw)
In-Reply-To: <Y5dR8X2mnytSCWrp@hovoldconsulting.com>
On Mon, Dec 12, 2022 at 05:08:17PM +0100, Johan Hovold wrote:
> The fact that USB core and driver core clears the pointer is an
> implementation detail which in principle could change.
With the new kerneldoc, the fact that the USB core clears the pointer
becomes part of the API. It is no longer an implementation detail but
rather a guarantee that drivers can depend on. (I.e., if it does
change, all the USB drivers will need to be audited.)
> The important
> part is that drivers generally should not touch the struct device or
> containing structure after unbind (and must do so with care otherwise).
While that certainly is an important point, it is not the point of
usb_set_intfdata() or its kerneldoc. The main reason for adding the
kerneldoc -- Vincent's original motivation -- was to inform coders that
drivers generally don't need to worry about clearing the data pointer.
A subtext was that clearing the pointer while the driver is still using
it can lead to problems, but I don't think we need to mention this.
It's pretty obvious.
Alan Stern
prev parent reply other threads:[~2022-12-12 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 12:06 [PATCH] USB: drop misleading usb_set_intfdata() kernel doc Johan Hovold
2022-12-12 10:19 ` Oliver Neukum
2022-12-12 10:31 ` Johan Hovold
2022-12-12 11:13 ` Oliver Neukum
2022-12-12 13:14 ` Johan Hovold
2022-12-12 13:27 ` Oliver Neukum
2022-12-12 13:40 ` Johan Hovold
2022-12-12 14:04 ` Oliver Neukum
2022-12-12 14:14 ` Johan Hovold
2022-12-12 15:25 ` Alan Stern
2022-12-12 16:08 ` Johan Hovold
2022-12-12 16:39 ` Alan Stern [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=Y5dZM68riR/EGn8W@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=oneukum@suse.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