Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	ksummit@lists.linux.dev
Subject: Re: [TECH TOPIC] Improving resource ownership and life-time in linux device drivers
Date: Wed,  9 Aug 2023 23:53:40 +0000	[thread overview]
Message-ID: <20230809235340.91584-1-sj@kernel.org> (raw)
In-Reply-To: <CACRpkdYtoD=OyoK_hyyORmUkcKcCM3m+GO1XUHdbmaS8gW0=BA@mail.gmail.com>

On Thu, 10 Aug 2023 00:03:20 +0200 Linus Walleij <linus.walleij@linaro.org> wrote:

> On Wed, Aug 9, 2023 at 8:05 PM Bartosz Golaszewski
> <bartosz.golaszewski@linaro.org> wrote:
> 
> > 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.
> 
> 1. Good topic.
> 
> 2. Is this also where we discuss the use of <linux/cleanup.h>
>     commit 54da6a0924311c7cf5015533991e44fb8eb12773
>     ? Because I would certainly like to learn more about that
>     thing with an example or two.

Plus one.


Thanks,
SJ

> 
> Yours,
> Linus Walleij
> 

  reply	other threads:[~2023-08-09 23:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 18:04 [TECH TOPIC] Improving resource ownership and life-time in linux device drivers Bartosz Golaszewski
2023-08-09 22:03 ` Linus Walleij
2023-08-09 23:53   ` SeongJae Park [this message]
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

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=20230809235340.91584-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=ksummit@lists.linux.dev \
    --cc=linus.walleij@linaro.org \
    --cc=peterz@infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).