All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Aleksandr Shabelnikov <mistermidi@gmail.com>,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH v2] firewire: core: bound traversal stack in read_config_rom()
Date: Wed, 3 Sep 2025 22:47:28 +0900	[thread overview]
Message-ID: <20250903134728.GA134568@workstation.local> (raw)
In-Reply-To: <20250903132048.GA77442@workstation.local>

On Wed, Sep 03, 2025 at 10:20:48PM +0900, Takashi Sakamoto wrote:
> Contributions to this subsystem may not provide a strong advantage to
> your career as a software engineer. However, knowledge and experience
> with the KUnit framework will certainly be valuable and beneficial. If
> you are still motivated, I encourage you to give it a try.

My collection of configuration ROM would be helpful to see the actual
content. They includes the ones from some music instruments:

* https://github.com/takaswie/am-config-roms/

When parsing the content, 'config-rom-pretty-printer' would be also
helpful, however I note that it has no support for "Extended_ROM entry"
in clause 7.7.18 of IEEE 1212:

https://git.kernel.org/pub/scm/utils/ieee1394/linux-firewire-utils.git/


Regards

Takashi Sakamoto

  reply	other threads:[~2025-09-03 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02  9:27 [PATCH v2] firewire: core: bound traversal stack in read_config_rom() Aleksandr Shabelnikov
2025-09-03 13:20 ` Takashi Sakamoto
2025-09-03 13:47   ` Takashi Sakamoto [this message]
2025-09-03 14:35     ` Aleksandr Shabelnikov

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=20250903134728.GA134568@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=mistermidi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.