mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: Richard Fitzgerald <rf@opensource.cirrus.com>,
	Lee Jones <lee@kernel.org>,
	alsa-devel@alsa-project.org, patches@opensource.cirrus.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 08/11] mfd: wm5110: Update to use maple tree register cache
Date: Tue, 18 Jul 2023 18:16:39 +0100	[thread overview]
Message-ID: <b7a1884c-77fb-41c7-b660-10d2d5d68aae@sirena.org.uk> (raw)
In-Reply-To: <20230718170035.GH103419@ediswmail.ad.cirrus.com>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Tue, Jul 18, 2023 at 05:00:35PM +0000, Charles Keepax wrote:
> On Tue, Jul 18, 2023 at 03:42:00PM +0000, Charles Keepax wrote:

> > This one appears to cause me some issues, seems to get the IRQs
> > into a weird state when doing compressed stream stuff. The
> > issue seems to also require commit bfa0b38c1483 ("regmap:
> > maple: Implement block sync for the maple tree cache") to be
> > present. So it definitely seems to relate to the cache sync,
> > but not sure if it is something todo with the device itself,
> > or the maple tree stuff yet.

> Ah... I think I see the regcache_sync sets async=true, but then
> the maple tree code immediately deletes the buffer after calling
> _regmap_raw_write. So its a racy use after free.

> How would we feel about having the maple tree code, clear async
> again?

I was going to say, it must be a maple tree issue.  I think we should
push that async down into the rbtree code, that's probably also broken
for other cache types if used in conjunction with slow buses...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-07-18 17:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13  0:49 [PATCH 00/11] mfd:: Update Cirrus Logic drivers to use maple tree register caches Mark Brown
2023-07-13  0:49 ` [PATCH 01/11] mfd: cs47l15: Update to use maple tree register cache Mark Brown
2023-07-13  0:49 ` [PATCH 02/11] mfd: cs47l24: " Mark Brown
2023-07-13  0:49 ` [PATCH 03/11] mfd: cs47l35: " Mark Brown
2023-07-13  0:49 ` [PATCH 04/11] mfd: cs47l85: " Mark Brown
2023-07-13  0:49 ` [PATCH 05/11] mfd: cs47l90: " Mark Brown
2023-07-13  0:49 ` [PATCH 06/11] mfd: cs47l92: " Mark Brown
2023-07-13  0:49 ` [PATCH 07/11] mfd: wm5102: " Mark Brown
2023-07-13  0:49 ` [PATCH 08/11] mfd: wm5110: " Mark Brown
2023-07-18 15:42   ` Charles Keepax
2023-07-18 17:00     ` Charles Keepax
2023-07-18 17:16       ` Mark Brown [this message]
2023-07-13  0:49 ` [PATCH 09/11] mfd: wm8994: " Mark Brown
2023-07-13  0:49 ` [PATCH 10/11] mfd: wm8997: " Mark Brown
2023-07-13  0:49 ` [PATCH 11/11] mfd: wm8998: " Mark Brown
2023-07-13 19:18 ` [PATCH 00/11] mfd:: Update Cirrus Logic drivers to use maple tree register caches Lee Jones

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=b7a1884c-77fb-41c7-b660-10d2d5d68aae@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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

all inboxes | Powered by JetHome®