From: Randy Dunlap <rdunlap@infradead.org>
To: Max Filippov <jcmvbkbc@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Cc: Matthew Wilcox <willy@infradead.org>, Yu Zhao <yuzhao@google.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Davidlohr Bueso <dave@stgolabs.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: /proc/*/maps broken on nommu
Date: Sun, 17 Sep 2023 08:06:51 -0700 [thread overview]
Message-ID: <e248c5c8-e55c-46eb-ae8d-f7539cdbeab2@infradead.org> (raw)
In-Reply-To: <CAMo8BfLb6U9xtMtt1t9vQX_nKek7kEt+Rvv5NwpvTHu0kdiXcg@mail.gmail.com>
On 9/17/23 04:38, Max Filippov wrote:
> Hello,
>
> As of v6.5 cat /proc/*/maps produces empty output on nommu xtensa systems.
> Bisection points to the commit 0c563f148043 ("proc: remove VMA rbtree
> use from nommu").
> It looks like the issue may be not in the m_start (where find_vma(mm,
> addr) returns
> NULL), but in the nommu version of find_vma itself. I've tried replacing nommu
> find_vma implementation with an implementation of the MMU version and it
> fixes the /proc/*/maps output. Kind of (it works as expected on one of
> my systems,
> but consistently locks up on the other).
>
> Any suggestions of what might be wrong/how to fix it properly?
>
Hi Max,
There is already a proposed patch and some discussion:
https://lore.kernel.org/lkml/20230915160055.971059-2-ben.wolsieffer@hefring.com/
--
~Randy
prev parent reply other threads:[~2023-09-17 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 11:38 Max Filippov
2023-09-17 15:06 ` Randy Dunlap [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=e248c5c8-e55c-46eb-ae8d-f7539cdbeab2@infradead.org \
--to=rdunlap@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yuzhao@google.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