From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] firewire: core: validate descriptor and sub-block lengths in fw_core_add_descriptor()
Date: Thu, 30 Jul 2026 22:03:38 +0900 [thread overview]
Message-ID: <20260730130338.GA276250@sakamocchi.jp> (raw)
In-Reply-To: <20260727174231.2816-1-sreekuttan2156239@gmail.com>
Hi,
On Mon, Jul 27, 2026 at 05:42:31PM +0000, Sreeraj S Kurup wrote:
> Hi Takashi,
>
> Thanks for applying the series to the for-next branch!
>
> Regarding the change in generate_config_rom():
>
> I dropped that specific change from this patchset to keep the series
> strictly focused on the out-of-bounds issue in fw_core_add_descriptor().
>
> `WARN_ON(j != config_rom_length)` acts as an assertion that the ROM block
> traversal matched the expected length. Replacing it with pr_warn() and
> clamping `config_rom_length = j` avoids a kernel warning splat, but if
> j != config_rom_length occurs, it indicates an unexpected state during
> ROM generation rather than a standard runtime condition.
>
> If you feel handling length mismatches gracefully via pr_warn() and updating
> config_rom_length is preferred over the WARN_ON assertion, I would be happy
> to send a follow-up patch for it.
Hm. The case that j does not equals to config_rom_length seems to be a
programming mistake and should be fixed immediately. So let me leave it
as is without any mitigation.
Thanks
Takashi Sakamoto
next prev parent reply other threads:[~2026-07-30 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 17:42 Sreeraj S Kurup
2026-07-30 13:03 ` Takashi Sakamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-25 15:52 Sreeraj S Kurup
2026-07-27 0:47 ` Takashi Sakamoto
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=20260730130338.GA276250@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=sreekuttan2156239@gmail.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
all inboxes | Powered by JetHome®