All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Cen Zhang <zzzccc427@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	perex@perex.cz, tiwai@suse.com, phucduc.bui@gmail.com,
	cezary.rojewski@intel.com, cassiogabrielcontato@gmail.com,
	kees+treewide@kernel.org, yilinzhang@moonshot.ai,
	sammiee5311@gmail.com, kees@kernel.org,
	thomas.weissschuh@linutronix.de, tglx@kernel.org,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	baijiaju1990@gmail.com, jjzuming@gmail.com
Subject: Re: [PATCH v2] ALSA: pcm: Unlink substreams before releasing them
Date: Thu, 15 Oct 2026 09:17:52 +0200	[thread overview]
Message-ID: <87qzhrmnz3.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAFRLqsX6Yz2dv_dV4BvV6_F-16WDWYTAk5ikC9WY7ZySkoJKUQ@mail.gmail.com>

On Thu, 15 Oct 2026 04:07:10 +0200,
Cen Zhang wrote:
> 
> Hi Takashi,
> 
> >
> > Applied to for-next branch now.
> >
> > A problem with racy link removal Sashiko suggested is an interesting
> > case to be revisited, but it's no regression and can be triggered
> > independently from this change.
> >
> >
> > Takashi
> 
> I saw that. The drain/unlink case looks like a real concurrency issue.
> I'll try to
> address it with a separate patch.

The patch I submitted yesterday is such an attempt:
  https://lore.kernel.org/20261014141212.316223-1-tiwai@suse.de

Unfortunately it couldn't be reviewed by Sashiko, as it's based on my
latest tree.  And now I noticed that there is still a potential race,
and fixed now.  Will resubmit v2 patch.


thanks,

Takashi

  reply	other threads:[~2026-10-15  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 10:52 [PATCH v2] ALSA: pcm: Unlink substreams before releasing them Cen Zhang
2026-10-14 12:54 ` Takashi Iwai
2026-10-15  2:07   ` Cen Zhang
2026-10-15  7:17     ` Takashi Iwai [this message]
2026-10-15 15:19       ` Cen Zhang
2026-10-15 15:35       ` Cen Zhang
2026-10-15 16:19         ` Takashi Iwai
2026-10-15 16:28           ` Cen Zhang

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=87qzhrmnz3.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=baijiaju1990@gmail.com \
    --cc=cassiogabrielcontato@gmail.com \
    --cc=cezary.rojewski@intel.com \
    --cc=jjzuming@gmail.com \
    --cc=kees+treewide@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=phucduc.bui@gmail.com \
    --cc=sammiee5311@gmail.com \
    --cc=tglx@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=tiwai@suse.com \
    --cc=yilinzhang@moonshot.ai \
    --cc=zzzccc427@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.