From: John Ogness <john.ogness@linutronix.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: firewire-ohci: 7.0.0-rc1 warnings+crash
Date: Sat, 28 Feb 2026 23:41:34 +0106 [thread overview]
Message-ID: <87bjh8ijih.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20260228031255.GA832746@workstation.local>
On 2026-02-28, Takashi Sakamoto <o-takashi@sakamocchi.jp> wrote:
> Thanks for the issue. It reports that the page array passed to vmap()
> includes any entries which have invalid PFN. I realize that the page
> array is passed to page_alloc_bulk() without zero initialization, thus
> it could include any garbage values.
>
> Would I ask you to apply the following patch and the issue is still
> regenerated or not?
With the patch applied, everything is working again. Thanks!
> ===== 8<- -----
> From 0d82ddae99869b231200d5247bbae586bf28274c Mon Sep 17 00:00:00 2001
> From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> Date: Sat, 28 Feb 2026 11:56:03 +0900
> Subject: [PATCH] firewire: ohci: initialize page array to use
> alloc_pages_bulk() correctly
>
> The call of alloc_pages_bulk() skips to fill entries of page array when
> the entries already have values. While, 1394 OHCI PCI driver passes the
> page array without initializing. It could cause invalid state at PFN
> validation in vmap().
>
> Fixes: f2ae92780ab9 ("firewire: ohci: split page allocation from dma mapping")
> Reported-by: John Ogness <john.ogness@linutronix.de>
> Closes: https://lore.kernel.org/lkml/87tsv1vig5.fsf@jogness.linutronix.de/
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Tested-by: John Ogness <john.ogness@linutronix.de>
prev parent reply other threads:[~2026-02-28 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 0:07 firewire-ohci: 7.0.0-rc1 warnings+crash John Ogness
2026-02-28 3:12 ` Takashi Sakamoto
2026-02-28 9:10 ` David Gow
2026-02-28 22:35 ` John Ogness [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=87bjh8ijih.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=o-takashi@sakamocchi.jp \
/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