From: Andrew Morton <akpm@linux-foundation•org>
To: Vlastimil Babka <vbabka@suse•cz>
Cc: Jani Nikula <jani.nikula@intel•com>,
Naresh Kamboju <naresh.kamboju@linaro•org>,
open list <linux-kernel@vger•kernel.org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
linux-mm <linux-mm@kvack•org>,
dri-devel@lists•freedesktop.org, Marco Elver <elver@google•com>,
Vijayanand Jitta <vjitta@codeaurora•org>,
Maarten Lankhorst <maarten.lankhorst@linux•intel.com>,
Maxime Ripard <mripard@kernel•org>,
Thomas Zimmermann <tzimmermann@suse•de>,
David Airlie <airlied@linux•ie>, Daniel Vetter <daniel@ffwll•ch>,
Andrey Ryabinin <ryabinin.a.a@gmail•com>,
Alexander Potapenko <glider@google•com>,
Andrey Konovalov <andreyknvl@gmail•com>,
Dmitry Vyukov <dvyukov@google•com>,
Geert Uytterhoeven <geert@linux-m68k•org>,
Oliver Glitta <glittao@gmail•com>,
Imran Khan <imran.f.khan@oracle•com>,
lkft-triage@lists•linaro.org,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Re: [next] [dragonboard 410c] Unable to handle kernel paging request at virtual address 00000000007c4240
Date: Thu, 21 Oct 2021 20:38:56 -0700 [thread overview]
Message-ID: <20211021203856.1151daebedef7b180fdfec22@linux-foundation.org> (raw)
In-Reply-To: <2a692365-cfa1-64f2-34e0-8aa5674dce5e@suse.cz>
On Thu, 21 Oct 2021 19:51:20 +0200 Vlastimil Babka <vbabka@suse•cz> wrote:
> >> Then we have to figure out how to order a fix between DRM and mmotm...
> >
> > That is the question! The problem exists only in the merge of the
> > two. On current DRM side stack_depot_init() exists but it's __init and
> > does not look safe to call multiple times. And obviously my changes
> > don't exist at all in mmotm.
> >
> > I guess one (admittedly hackish) option is to first add a patch in
> > drm-next (or drm-misc-next) that makes it safe to call
> > stack_depot_init() multiple times in non-init context. It would be
> > dropped in favour of your changes once the trees get merged together.
> >
> > Or is there some way for __drm_stack_depot_init() to detect whether it
> > should call stack_depot_init() or not, i.e. whether your changes are
> > there or not?
>
> Let's try the easiest approach first. AFAIK mmotm series is now split to
> pre-next and post-next part
It has been this way for many years!
> and moving my patch
> lib-stackdepot-allow-optional-init-and-stack_table-allocation-by-kvmalloc.patch
> with the following fixup to the post-next part should solve this. Would that
> work, Andrew? Thanks.
For this reason. No probs, thanks.
I merge up the post-linux-next parts late in the merge window. I do
need to manually check that the prerequisites are in mainline, because
sometimes the patches apply OK but don't make sense.
next prev parent reply other threads:[~2021-10-22 3:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 18:24 [next] [dragonboard 410c] Unable to handle kernel paging request at virtual address 00000000007c4240 Naresh Kamboju
2021-10-21 7:51 ` Vlastimil Babka
2021-10-21 8:40 ` Jani Nikula
2021-10-21 17:51 ` Vlastimil Babka
2021-10-22 3:38 ` Andrew Morton [this message]
2021-10-22 7:43 ` Vlastimil Babka
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=20211021203856.1151daebedef7b180fdfec22@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=airlied@linux$(echo .)ie \
--cc=andreyknvl@gmail$(echo .)com \
--cc=daniel@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=dvyukov@google$(echo .)com \
--cc=elver@google$(echo .)com \
--cc=geert@linux-m68k$(echo .)org \
--cc=glider@google$(echo .)com \
--cc=glittao@gmail$(echo .)com \
--cc=imran.f.khan@oracle$(echo .)com \
--cc=jani.nikula@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=maarten.lankhorst@linux$(echo .)intel.com \
--cc=mripard@kernel$(echo .)org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=ryabinin.a.a@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tzimmermann@suse$(echo .)de \
--cc=vbabka@suse$(echo .)cz \
--cc=vjitta@codeaurora$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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