From: Vladis Dronov <vdronov@redhat.com>
To: Andrea Righi <andrea.righi@canonical.com>,
Colin Ian King <colin.king@canonical.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ptp: free ptp clock properly
Date: Fri, 3 Apr 2020 09:34:14 -0400 (EDT) [thread overview]
Message-ID: <1196893766.20531178.1585920854778.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200309172238.GJ267906@xps-13>
Hello, Andrea, Colin, all,
This fix is really not needed, as its creation is based on the assumption
that the Ubuntu kernel 5.3.0-40-generic has the upstream commit 75718584cb3c,
which is the real fix to this crash.
> > > I would guess that a kernel in question (5.3.0-40-generic) has the commit
> > > a33121e5487b but does not have the commit 75718584cb3c, which should be
> > > exactly fixing a docking station disconnect crash. Could you please,
> > > check this?
> >
> > Unfortunately the kernel in question already has 75718584cb3c:
> > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe&id=c71b774732f997ef38ed7bd62e73891a01f2bbfe
Apologies, but the assumption above is not correct, 5.3.0-40-generic does
not have 75718584cb3c. If it had 75718584cb3c it would be a fix and the ptp-related
crash (described in https://bugs.launchpad.net/bugs/1864754) would not happen.
This way https://lists.ubuntu.com/archives/kernel-team/2020-March/108562.html fix
is not really needed.
Best regards,
Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer
----- Original Message -----
> From: "Andrea Righi" <andrea.righi@canonical.com>
> To: "Richard Cochran" <richardcochran@gmail.com>, "Vladis Dronov" <vdronov@redhat.com>
> Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
> Sent: Monday, March 9, 2020 6:22:38 PM
> Subject: [PATCH v2] ptp: free ptp clock properly
>
> There is a bug in ptp_clock_unregister() where pps_unregister_source()
> can free up resources needed by posix_clock_unregister() to properly
> destroy a related sysfs device.
>
> Fix this by calling pps_unregister_source() in ptp_clock_release().
>
> See also:
> commit 75718584cb3c ("ptp: free ptp device pin descriptors properly").
>
> BugLink: https://bugs.launchpad.net/bugs/1864754
> Fixes: a33121e5487b ("ptp: fix the race between the release of ptp_clock and
> cdev")
> Tested-by: Piotr Morgwai Kotarbiński <foss@morgwai.pl>
> Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
> ---
>
> v2: move pps_unregister_source() to ptp_clock_release(), instead of
> posix_clock_unregister(), that would just introduce a resource leak
>
> drivers/ptp/ptp_clock.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/ptp/ptp_clock.c b/drivers/ptp/ptp_clock.c
> index ac1f2bf9e888..468286ef61ad 100644
> --- a/drivers/ptp/ptp_clock.c
> +++ b/drivers/ptp/ptp_clock.c
> @@ -170,6 +170,9 @@ static void ptp_clock_release(struct device *dev)
> {
> struct ptp_clock *ptp = container_of(dev, struct ptp_clock, dev);
>
> + /* Release the clock's resources. */
> + if (ptp->pps_source)
> + pps_unregister_source(ptp->pps_source);
> ptp_cleanup_pin_groups(ptp);
> mutex_destroy(&ptp->tsevq_mux);
> mutex_destroy(&ptp->pincfg_mux);
> @@ -298,11 +301,6 @@ int ptp_clock_unregister(struct ptp_clock *ptp)
> kthread_cancel_delayed_work_sync(&ptp->aux_work);
> kthread_destroy_worker(ptp->kworker);
> }
> -
> - /* Release the clock's resources. */
> - if (ptp->pps_source)
> - pps_unregister_source(ptp->pps_source);
> -
> posix_clock_unregister(&ptp->clock);
>
> return 0;
> --
> 2.25.0
next prev parent reply other threads:[~2020-04-03 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 17:22 [PATCH v2] ptp: free ptp clock properly Andrea Righi
2020-03-10 2:57 ` Richard Cochran
2020-04-03 13:34 ` Vladis Dronov [this message]
2020-04-07 9:34 ` Andrea Righi
2020-04-07 10:05 ` Vladis Dronov
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=1196893766.20531178.1585920854778.JavaMail.zimbra@redhat.com \
--to=vdronov@redhat.com \
--cc=andrea.righi@canonical.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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;
as well as URLs for NNTP newsgroup(s).