All of lore.kernel.org
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH] USB: serial: mos7720: defer state restore to a workqueue
Date: Mon, 16 Nov 2020 14:31:02 -0800	[thread overview]
Message-ID: <20201116223102.eliwt7uh5rkiiq5h@linux-p48b.lan> (raw)
In-Reply-To: <X7KyPrY8FDH4C/gm@localhost>

On Mon, 16 Nov 2020, Johan Hovold wrote:

>On Fri, Nov 13, 2020 at 08:27:25PM -0800, Davidlohr Bueso wrote:
>> @@ -1883,21 +1724,17 @@ static void mos7720_release(struct usb_serial *serial)
>>		if (mos_parport->msg_pending)
>>			wait_for_completion_timeout(&mos_parport->syncmsg_compl,
>>					    msecs_to_jiffies(MOS_WDR_TIMEOUT));
>> +		/*
>> +		 * If delayed work is currently scheduled, wait for it to
>> +		 * complete. This also implies barriers that ensure the
>> +		 * below serial clearing is not hoisted above the ->work.
>> +		 */
>> +		cancel_work_sync(&mos_parport->work);
>
>As I mentioned, this needs to be done *after* deregistering the port or
>you could theoretically end up with the work item being requeued.

Hmm sorry yes I forgot to mention this. I was counting on the private_data
already being null to prevent any new work being actually scheduled, so an
incoming restore state, for example, would be a nop.

>
>Yes, the same applies for the "synchronous" requests, but that's a
>preexisting issue.

Per the above I also assumed sync requests were also safe as is.

But I can certainly re-order things, how about:

mos7720_release():
    mos_parport->pp->private_data = NULL;
    parport_remove_port(mos_parport->pp);

    wait_for_completion_timeout();
    cancel_work_sync();

    usb_set_serial_data(serial, NULL);
    mos_parport->serial = NULL;

    parport_del_port(mos_parport->pp);
    kref_put();

Thanks,
Davidlohr

  reply	other threads:[~2020-11-16 22:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 21:14 [PATCH] usb/mos7720: process deferred urbs in a workqueue Davidlohr Bueso
2020-11-03 20:40 ` Davidlohr Bueso
2020-11-04 11:06   ` Johan Hovold
2020-11-04 16:25     ` Johan Hovold
2020-11-05  0:13       ` Davidlohr Bueso
2020-11-05  8:25         ` Johan Hovold
2020-11-06  6:17           ` Davidlohr Bueso
2020-11-09  9:22             ` Oliver Neukum
2020-11-09 19:14               ` Davidlohr Bueso
2020-11-13  9:14             ` Johan Hovold
2020-11-14  4:27               ` [PATCH] USB: serial: mos7720: defer state restore to " Davidlohr Bueso
2020-11-16 17:09                 ` Johan Hovold
2020-11-16 22:31                   ` Davidlohr Bueso [this message]
2020-11-17 16:28                     ` Johan Hovold
2020-11-17 16:48                       ` [PATCH v2] " Davidlohr Bueso
2020-11-18 10:11                         ` Johan Hovold
2020-11-20  4:53                           ` [PATCH v3] " Davidlohr Bueso
2020-11-20  9:37                             ` 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=20201116223102.eliwt7uh5rkiiq5h@linux-p48b.lan \
    --to=dave@stgolabs.net \
    --cc=dbueso@suse.de \
    --cc=johan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.