From: Greg KH <gregkh@linuxfoundation.org>
To: hailong.liu@oppo.com
Cc: hailong.liu.linux@outlook.com, stable@vger.kernel.org
Subject: Re: [PATCH v3] mm/vmalloc: fix corrupted list of vbq->free
Date: Sun, 2 Jun 2024 09:15:25 +0200 [thread overview]
Message-ID: <2024060248-unsold-growing-8ec7@gregkh> (raw)
In-Reply-To: <20240601161819.8229-1-hailong.liu@oppo.com>
On Sun, Jun 02, 2024 at 12:18:19AM +0800, hailong.liu@oppo.com wrote:
> From: "Hailong.Liu" <hailong.liu@oppo.com>
>
> The function xa_for_each() in _vm_unmap_aliases() loops through all
> vbs. However, since commit 062eacf57ad9 ("mm: vmalloc: remove a global
> vmap_blocks xarray") the vb from xarray may not be on the corresponding
> CPU vmap_block_queue. Consequently, purge_fragmented_block() might
> use the wrong vbq->lock to protect the free list, leading to vbq->free
> breakage.
<snip>
Did you forget to cc: the relevant developers for this change?
stable@vger.kernel.org is not the proper place to do mm development
work.
thanks,
greg k-h
next prev parent reply other threads:[~2024-06-02 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 16:18 [PATCH v3] mm/vmalloc: fix corrupted list of vbq->free hailong.liu
2024-06-02 7:15 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-01 17:13 hailong.liu
2024-06-01 17:46 ` Hailong Liu
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=2024060248-unsold-growing-8ec7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hailong.liu.linux@outlook.com \
--cc=hailong.liu@oppo.com \
--cc=stable@vger.kernel.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