From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] maple_tree: Disable mas_wr_append() when other readers are possible
Date: Mon, 16 Oct 2023 10:29:14 +0200 [thread overview]
Message-ID: <3e1f079f-a0a7-43b3-96db-24c2e04d5ff8@leemhuis.info> (raw)
In-Reply-To: <7e9735bf-c42b-4f03-8645-8cdbf87a75f3@leemhuis.info>
On 11.09.23 14:27, Linux regression tracking #adding (Thorsten Leemhuis)
wrote:
> On 29.08.23 18:42, Geert Uytterhoeven wrote:
>>
>> On Fri, 18 Aug 2023, Liam R. Howlett wrote:
>>> The current implementation of append may cause duplicate data and/or
>>> incorrect ranges to be returned to a reader during an update. Although
>>> this has not been reported or seen, disable the append write operation
>>> while the tree is in rcu mode out of an abundance of caution.
>>>
>>> During the analysis of the mas_next_slot() the following was
>>> artificially created by separating the writer and reader code:
>> [...]
>> Thanks for your patch, which is now commit cfeb6ae8bcb96ccf
>> ("maple_tree: disable mas_wr_append() when other readers are
>> possible") in v6.5, and is being backported to stable.
>>
>> On Renesas RZ/A1 and RZ/A2 (single-core Cortex-A9), this causes the
>> following warning:
>>> […]
>> Reverting this commit fixes the issue.
#regzbot fix: cff9b2332ab762
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
next prev parent reply other threads:[~2023-10-16 8:29 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 0:43 [PATCH v2 0/2] maple_tree: mas_wr_append() fix ups Liam R. Howlett
2023-08-19 0:43 ` [PATCH v2 1/2] maple_tree: Disable mas_wr_append() when other readers are possible Liam R. Howlett
2023-08-29 16:42 ` Geert Uytterhoeven
2023-08-31 5:39 ` Michael Ellerman
2023-08-31 8:25 ` Geert Uytterhoeven
2023-08-31 8:45 ` Peng Zhang
2023-08-31 9:43 ` Geert Uytterhoeven
2023-09-06 15:23 ` Liam R. Howlett
2023-09-06 17:23 ` Paul E. McKenney
2023-09-06 17:29 ` Liam R. Howlett
2023-09-06 18:02 ` Paul E. McKenney
2023-09-11 23:54 ` Liam R. Howlett
2023-09-12 8:14 ` Paul E. McKenney
2023-09-12 8:23 ` Geert Uytterhoeven
2023-09-12 8:30 ` Paul E. McKenney
2023-09-12 8:34 ` Geert Uytterhoeven
2023-09-12 10:00 ` Paul E. McKenney
2023-09-12 13:56 ` Liam R. Howlett
2023-09-12 14:29 ` Liam R. Howlett
2023-09-12 15:08 ` Paul E. McKenney
2023-09-12 15:27 ` Christophe Leroy
2023-09-12 15:49 ` Liam R. Howlett
2023-09-12 15:07 ` Paul E. McKenney
2023-09-12 15:44 ` Liam R. Howlett
2023-09-12 16:49 ` Paul E. McKenney
2023-09-12 17:02 ` Christophe Leroy
2023-09-12 17:09 ` Christophe Leroy
2023-09-12 17:38 ` Liam R. Howlett
2023-09-13 13:14 ` Geert Uytterhoeven
2023-09-13 13:24 ` Liam R. Howlett
2023-09-13 13:26 ` Geert Uytterhoeven
2023-09-12 14:37 ` Christophe Leroy
2023-09-12 14:10 ` Matthew Wilcox
2023-09-12 14:17 ` Liam R. Howlett
2023-09-06 19:06 ` Geert Uytterhoeven
2023-09-11 12:27 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-10-16 8:29 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
2023-08-30 19:49 ` Andreas Schwab
2023-08-31 5:37 ` Michael Ellerman
2023-08-31 19:01 ` Andreas Schwab
2023-09-12 18:15 ` Andreas Schwab
2023-09-12 19:09 ` Liam R. Howlett
2023-09-12 20:01 ` Andreas Schwab
2023-08-19 0:43 ` [PATCH v2 2/2] maple_tree: Clean up mas_wr_append() Liam R. Howlett
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=3e1f079f-a0a7-43b3-96db-24c2e04d5ff8@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=regressions@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