public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Salah Triki <salah.triki@gmail.com>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: H Hartley Sweeten <hsweeten@visionengravers.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] comedi: fix device lifecycle handling in comedi_dev_kref_release()
Date: Wed, 4 Feb 2026 21:46:32 +0100	[thread overview]
Message-ID: <aYOwKLWgNUvD1WVV@pc> (raw)
In-Reply-To: <e538d495-fd55-4e63-9256-cb0eed259a6b@mev.co.uk>

On Mon, Feb 02, 2026 at 03:12:29PM +0000, Ian Abbott wrote:
> On 02/02/2026 12:09, Ian Abbott wrote:
> > NAK
> > 
> > This isn't freeing the `struct device`, it is freeing the `struct
> > comedi_device`.  The `struct device` will be freed by
> > `device_create_release()` in "drivers/base/core.c".
> 
> To clarify, the call to `put_device()` from `comedi_dev_kref_release()`
> matches the call to `get_device()` after a successful call to
> `device_create()` from `comedi_alloc_board_minor()`.
> 
> The counterpart to `comedi_alloc_board_minor()` is `comedi_free_board_dev()`
> which calls `device_destroy()` (matching the call to `device_create()`),
> followed by a call to `comedi_dev_put()`. `comedi_dev_put()` will call
> `comedi_dev_kref_release()` via `kref_put()` when its reference count
> reaches zero, and as mentioned previously, its call to `put_device()`
> matches the previous call to `get_device()` after the device was created.
> So there are no hooks back to the comedi module code or the `struct
> comedi_device` at that point because the `struct device` has already been
> removed from the system.
> 
> The reason for the extra calls to `get_device()` and `put_device()` is
> explained by commit 8f988d8784e3 ("staging/comedi: keep reference to class
> device after destroyed").
> 
> -- 
> -=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company  )=-
> -=( registered in England & Wales.  Regd. number: 02862268.  )=-
> -=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
> -=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-

Thanks for the detailed explanation, that makes sense. I’ll drop this patch.

Best regards,
Salah

      reply	other threads:[~2026-02-04 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 22:35 [PATCH] comedi: fix device lifecycle handling in comedi_dev_kref_release() Salah Triki
2026-02-02 12:09 ` Ian Abbott
2026-02-02 15:12   ` Ian Abbott
2026-02-04 20:46     ` Salah Triki [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=aYOwKLWgNUvD1WVV@pc \
    --to=salah.triki@gmail.com \
    --cc=abbotti@mev.co.uk \
    --cc=hsweeten@visionengravers.com \
    --cc=linux-kernel@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