Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@alsa-project.org
Cc: Curtis Malainey <cujomalainey@google.com>
Subject: Re: [PATCH RFC 0/9] ALSA: Don't embed struct devices
Date: Thu, 17 Aug 2023 09:27:35 +0200	[thread overview]
Message-ID: <874jkyw2l4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230816160252.23396-1-tiwai@suse.de>

On Wed, 16 Aug 2023 18:02:43 +0200,
Takashi Iwai wrote:
> 
> Hi,
> 
> this is another set of patches to attempt papering over the UAF
> problems that are seen when the delayed kobject release is enabled, as
> initially reported by Curtis:
>   https://lore.kernel.org/r/20230801171928.1460120-1-cujomalainey@chromium.org
> 
> There was a previous patch set with a different approach (using the
> device refcount dependencies), but this is a sort of step-back to the
> old way.
>   https://lore.kernel.org/r/20230807135207.17708-1-tiwai@suse.de
> 
> After discussions and evaluations, we agreed that decoupling the
> struct device from each sound component object is the safest (and
> easiest) way as of now.  For applying the changes more consistently, I
> introduced a new helper for the struct device allocation and
> initialization, and applied all components.
> 
> A couple of more changes for card_dev refcount managed aren't included
> in this patch set, though.  They might be good to have, but this patch
> set should suffice for the currently seen UAF problems.
> 
> For a long-term solution, we may restructure the device management,
> then the struct devices may be embedded again in each object.  But,
> it'll need lots of other changes and cleanups, a big TODO.
> 
> The latest patches are found in topic/dev-split branch of sound.git
> tree.
> 
> 
> Takashi
> 
> ===
> 
> Takashi Iwai (9):
>   ALSA: core: Introduce snd_device_alloc()
>   ALSA: control: Don't embed ctl_dev
>   ALSA: pcm: Don't embed device
>   ALSA: hwdep: Don't embed device
>   ALSA: rawmidi: Don't embed device
>   ALSA: compress: Don't embed device
>   ALSA: timer: Create device with snd_device_alloc()
>   ALSA: seq: Create device with snd_device_alloc()
>   ALSA: core: Drop snd_device_initialize()

Although the patch set was sent as RFC, I merged them now for 6.6 with
Acks, as there is no further plan to change.


thanks,

Takashi

      parent reply	other threads:[~2023-08-17  7:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 16:02 [PATCH RFC 0/9] ALSA: Don't embed struct devices Takashi Iwai
2023-08-16 16:02 ` [PATCH RFC 1/9] ALSA: core: Introduce snd_device_alloc() Takashi Iwai
2023-08-16 16:02 ` [PATCH RFC 2/9] ALSA: control: Don't embed ctl_dev Takashi Iwai
2023-08-16 16:02 ` [PATCH RFC 3/9] ALSA: pcm: Don't embed device Takashi Iwai
2023-08-16 16:02 ` [PATCH RFC 4/9] ALSA: hwdep: " Takashi Iwai
2023-08-16 16:02 ` [PATCH RFC 5/9] ALSA: rawmidi: " Takashi Iwai
2023-08-16 16:02 ` [PATCH RFC 6/9] ALSA: compress: " Takashi Iwai
2023-08-16 16:02 ` [PATCH RFC 7/9] ALSA: timer: Create device with snd_device_alloc() Takashi Iwai
2023-08-16 16:02 ` [PATCH RFC 8/9] ALSA: seq: " Takashi Iwai
2023-08-16 16:02 ` [PATCH RFC 9/9] ALSA: core: Drop snd_device_initialize() Takashi Iwai
2023-08-16 16:45 ` [PATCH RFC 0/9] ALSA: Don't embed struct devices Jaroslav Kysela
2023-08-16 22:18   ` Curtis Malainey
2023-08-17  7:27 ` Takashi Iwai [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=874jkyw2l4.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=cujomalainey@google.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