linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Wei Yang <richard.weiyang@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	kernel test robot <oliver.sang@intel.com>,
	oe-lkp@lists.linux.dev, lkp@intel.com,
	Matthew Wilcox <willy@infradead.org>,
	maple-tree@lists.infradead.org, linux-mm@kvack.org
Subject: Re: [linux-next:master] [maple_tree]  540335e987: BUG:kernel_NULL_pointer_dereference,address
Date: Tue, 24 Jun 2025 06:59:02 +0000	[thread overview]
Message-ID: <20250624065902.7c5d5jrhjxvwjvpq@master> (raw)
In-Reply-To: <5f5fyv7kcaah4o4lnj6mc2zpptu5v27iajbpahykgakgzz3z2w@spevx4qf2aph>

On Mon, Jun 23, 2025 at 05:19:07PM -0400, Liam R. Howlett wrote:
[...]
>
>This will need to be addressed once the dense nodes arrive, but it
>really should not happen right now.
>
>I don't like the idea of checking this every time we walk a node, if it
>can be avoided.
>
>> 
>> Sorry for the trouble. It is better to drop it.
>
>This indicates another issue exists which was exposed with your fix.
>
>I've tracked it down to the maple status being restored to ma_active
>before the maple state node is set.  The bot looks to have hit this by
>going mas_prev() on 0 and getting the status to ma_underflow, then
>mas_find(), which restored it to ma_active and tried to walk when the
>node was NULL in mas_find_setup().
>

The analysis looks reasonable. Thanks for your time.

>I have a fix for this and I'll roll your change into my fix and add you
>as the reporter... and add links to the resend, v3 patches, and this
>thread.  Stable will be excluded because it's really not worth the risk
>- the code is stable now but just suboptimal.
>
>This still leaves your initial patch 1 and 3, which has nothing to do
>with either of these bugs that you included in the patch set.  It is
>best to keep patches related to each other together, but not include
>things you find while developing those fixes, specifically for this
>scenario.
>
>I will grab those patches and re-examine them before sending them along,
>again.
>
>Thanks,
>Liam

-- 
Wei Yang
Help you, Help me


      reply	other threads:[~2025-06-24  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  7:32 kernel test robot
2025-06-19 22:44 ` Andrew Morton
2025-06-20  2:14   ` Wei Yang
2025-06-23 21:19     ` Liam R. Howlett
2025-06-24  6:59       ` Wei Yang [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=20250624065902.7c5d5jrhjxvwjvpq@master \
    --to=richard.weiyang@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=maple-tree@lists.infradead.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=willy@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