ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Greg KH <greg@kroah.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	ksummit@lists.linux.dev
Subject: Re: [TECH TOPIC] Improving resource ownership and life-time in linux device drivers
Date: Thu, 10 Aug 2023 23:47:13 +0300	[thread overview]
Message-ID: <20230810204713.GF402@pendragon.ideasonboard.com> (raw)
In-Reply-To: <2023081048-skittle-excusable-2c9f@gregkh>

On Thu, Aug 10, 2023 at 05:47:02PM +0200, Greg KH wrote:
> On Wed, Aug 09, 2023 at 08:04:39PM +0200, 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.
> 
> I'm all for this, we need some major work in this area.

Likewise. I will however not be physically present at the kernel summit
this year, but plan to participate remotely.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2023-08-10 20:47 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 [this message]
2023-08-14  9:27     ` Wolfram Sang
2023-08-15  3:05   ` Herrenschmidt, Benjamin
2023-08-10 19:07 ` Julia Lawall

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=20230810204713.GF402@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=greg@kroah.com \
    --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