Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <FA654A0D-29B7-4B6B-B613-73598A92ADA8@goldelico.com>
 <YmkBAsa+fKlp/GcV@atomide.com> <CAK8P3a3N9WBWC_ECB0pSRHUCT4iz=tdT+Dt9Cyd5Wh3qEaVqqA@mail.gmail.com>
 <4CE23DC3-B3E5-45C1-91F3-B88E5444AE7C@goldelico.com> <CAK8P3a3EFfF0gr5kFkboRfJifrY-D+NgHFekBfSePWuY2c8PMA@mail.gmail.com>
 <11504A17-6B50-4D6C-A9E1-CA943C157C93@goldelico.com> <CAK8P3a2RN77ajZD4xRhKsqozPizneLcLYhm0rTE6qX25-4cJsw@mail.gmail.com>
In-Reply-To: <CAK8P3a2RN77ajZD4xRhKsqozPizneLcLYhm0rTE6qX25-4cJsw@mail.gmail.com>
From:   Ard Biesheuvel <ardb@kernel.org>
Date:   Tue, 3 May 2022 09:28:44 +0200
Message-ID: <CAMj1kXHqHCt9G+HEawsWmba2Z=WVbp6wRrivAQvQCn2iph9kXg@mail.gmail.com>
Subject: Re: kernel panic with v5.18-rc1 on OpenPandora (only)
To:     Arnd Bergmann <arnd@arndb.de>
Cc:     "H. Nikolaus Schaller" <hns@goldelico.com>,
        Tony Lindgren <tony@atomide.com>,
        Discussions about the Letux Kernel 
        <letux-kernel@openphoenux.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux-OMAP <linux-omap@vger.kernel.org>,
        Linux ARM <linux-arm-kernel@lists.infradead.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Sat, 30 Apr 2022 at 20:48, Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Sat, Apr 30, 2022 at 7:18 PM H. Nikolaus Schaller <hns@goldelico.com> wrote:
> > > Am 30.04.2022 um 17:36 schrieb Arnd Bergmann <arnd@arndb.de>:
> > >
> > >
> > > I suppose this could be anywhere then. The backtrace seems to point
> > > to re-enabling interupts in do_work_pending, so something probably
> > > accessed DMA memory asynchronously.
> >
> > Yes. I now (or still) sometimes see the same omap l3 irq issue when plugging in/out the USB/OTG
> > cable. Not with a kernel panic, but in the same driver omap_l3_smx.c.
> > This happens even if the wl1251 driver is removed.
>
> Is this also a regression, or did it happen before the vmap-stack
> change? If this only
> appeared now, then this points to another bug somewhere that you
> should find using
> CONFIG_DMA_API_DEBUG.
>
> I think what is going on here is that your platform is able to detect
> the broken DMA
> because of the l3 interrupt handler telling the kernel about it, when
> on other platforms
> we would see either silent data corruption or a DMA that never reaches
> its target.
>

I wonder if we could narrow this down by adding the possibility to use
IRQ stacks in the linear map, while using vmap'ed task stacks.