ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: ksummit@lists.linux.dev
Subject: Re: [TECH TOPIC] Improving resource ownership and life-time in linux device drivers
Date: Thu, 10 Aug 2023 21:07:26 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2308102107110.3802@hadrien> (raw)
In-Reply-To: <CACMJSev18ZdTVDK7j3gCpzw4rAiaNMZRT4KSvLzd99H61XwMOA@mail.gmail.com>



On Wed, 9 Aug 2023, Bartosz Golaszewski wrote:

> Hi!
>
> I submitted this proposal on time using the website but forgot about
> sending it here too. Hope that's alright. The abstract follows.
>
> Bartosz Golaszewski
>
> --
>
> Recently there have been several talks about issues with object
> ownership in device drivers, use-after-free bugs and problems with
> handling hot unplug events in certain subsystems.
>
> First Laurent Pinchart revisited an older discussion about the harmful
> side-effects of devres helpers during LPC 2022[1]. I then went down
> that rabbit hole only to discover a whole suite of issues, not really
> linked to devres in any way but rather mostly caused by the way
> subsystems and drivers mix reference counted resources with regular
> ones[2]. This year Wolfram Sang continued the research and presented
> even more vulnerable subsystems as well as some potential remedies
> during his talk at the EOSS 2023 in Prague[3].
>
> I have since experimented with several approaches and would like to
> present some updates on this subject. During this talk I plan to jump
> straight into presenting concrete ideas and timelines for improving
> the driver model and introducing some unification in the way
> subsystems handle driver data. While this is a significant effort
> spanning multiple device subsystems that will need to be carried out
> in many phases over what will most likely be years, without addressing
> the problems, we'll be left with many parts of the kernel not being
> able to correctly handle simple driver unbinds.
>
> [1] https://lpc.events/event/16/contributions/1227/
> [2] https://fosdem.org/2023/schedule/event/devm_kzalloc/
> [3] https://eoss2023.sched.com/event/1LcPP/subsystems-with-object-lifetime-issues-in-the-embedded-case-wolfram-sang-sang-engineering-renesas

I will be very interested in seeing this talk.

julia

      parent reply	other threads:[~2023-08-10 19:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 18:04 Bartosz Golaszewski
2023-08-09 22:03 ` Linus Walleij
2023-08-09 23:53   ` SeongJae Park
2023-08-10  7:55   ` Bartosz Golaszewski
2023-08-10 15:47 ` Greg KH
2023-08-10 20:47   ` Laurent Pinchart
2023-08-14  9:27     ` Wolfram Sang
2023-08-15  3:05   ` Herrenschmidt, Benjamin
2023-08-10 19:07 ` Julia Lawall [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=alpine.DEB.2.22.394.2308102107110.3802@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=ksummit@lists.linux.dev \
    /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