linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Johan Hovold <johan@kernel.org>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
	linux-usb@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] usb: xhci: dbc: get rid of global pointer
Date: Mon, 17 Jun 2019 09:43:19 +0300	[thread overview]
Message-ID: <877e9kiuew.fsf@linux.intel.com> (raw)
In-Reply-To: <20190614145236.GB3849@localhost>

[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]


Hi,

Johan Hovold <johan@kernel.org> writes:
> On Tue, Jun 11, 2019 at 08:24:16PM +0300, Felipe Balbi wrote:
>> If we happen to have two XHCI controllers with DbC capability, then
>> there's no hope this will ever work as the global pointer will be
>> overwritten by the controller that probes last.
>> 
>> Avoid this problem by keeping the tty_driver struct pointer inside
>> struct xhci_dbc.
>
> How did you test this patch?

by running it on a machine that actually has two DbCs

>> @@ -279,52 +279,52 @@ static const struct tty_operations dbc_tty_ops = {
>>  	.unthrottle		= dbc_tty_unthrottle,
>>  };
>>  
>> -static struct tty_driver *dbc_tty_driver;
>> -
>>  int xhci_dbc_tty_register_driver(struct xhci_hcd *xhci)
>>  {
>>  	int			status;
>>  	struct xhci_dbc		*dbc = xhci->dbc;
>>  
>> -	dbc_tty_driver = tty_alloc_driver(1, TTY_DRIVER_REAL_RAW |
>> +	dbc->tty_driver = tty_alloc_driver(1, TTY_DRIVER_REAL_RAW |
>>  					  TTY_DRIVER_DYNAMIC_DEV);
>> -	if (IS_ERR(dbc_tty_driver)) {
>> -		status = PTR_ERR(dbc_tty_driver);
>> -		dbc_tty_driver = NULL;
>> +	if (IS_ERR(dbc->tty_driver)) {
>> +		status = PTR_ERR(dbc->tty_driver);
>> +		dbc->tty_driver = NULL;
>>  		return status;
>>  	}
>>  
>> -	dbc_tty_driver->driver_name = "dbc_serial";
>> -	dbc_tty_driver->name = "ttyDBC";
>> +	dbc->tty_driver->driver_name = "dbc_serial";
>> +	dbc->tty_driver->name = "ttyDBC";
>
> You're now registering multiple drivers for the same thing (and wasting
> a major number for each) and specifically using the same name, which
> should lead to name clashes when registering the second port.

No warnings were printed while running this, actually. Odd

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-06-17  6:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 17:24 [PATCH] usb: xhci: dbc: get rid of global pointer Felipe Balbi
2019-06-14 12:26 ` Mathias Nyman
2019-06-14 14:52 ` Johan Hovold
2019-06-17  6:43   ` Felipe Balbi [this message]
2019-06-18 14:31     ` Johan Hovold
2019-06-19  6:33       ` Felipe Balbi
2019-06-19  7:27         ` Mathias Nyman
2019-06-19 12:14         ` Johan Hovold

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=877e9kiuew.fsf@linux.intel.com \
    --to=felipe.balbi@linux.intel.com \
    --cc=johan@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=stable@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).