From: Sudeep Holla <sudeep.holla@arm.com>
To: Johan Hovold <johan@kernel.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
arm-scmi@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Jan Palus <jpalus@fastmail.com>
Subject: Re: [PATCH] firmware: arm_scmi: quirk: fix write to string constant
Date: Tue, 2 Sep 2025 12:18:37 +0100 [thread overview]
Message-ID: <20250902-original-hallowed-robin-d030bf@sudeepholla> (raw)
In-Reply-To: <aLbGoctnA-Ad-Hxv@hovoldconsulting.com>
On Tue, Sep 02, 2025 at 12:27:45PM +0200, Johan Hovold wrote:
> On Tue, Sep 02, 2025 at 11:16:46AM +0100, Sudeep Holla wrote:
> > On Tue, Sep 02, 2025 at 11:59:24AM +0200, Johan Hovold wrote:
> > > On Fri, Aug 29, 2025 at 04:29:48PM +0200, Johan Hovold wrote:
> > > > On Fri, Aug 29, 2025 at 03:21:52PM +0200, Johan Hovold wrote:
>
> > > > > The quirk version range is typically a string constant and must not be
> > > > > modified (e.g. as it may be stored in read-only memory):
> > > > >
> > > > > Unable to handle kernel write to read-only memory at virtual
> > > > > address ffffc036d998a947
> > > > >
> > > > > Fix the range parsing so that it operates on a copy of the version range
> > > > > string, and mark all the quirk strings as const to reduce the risk of
> > > > > introducing similar future issues.
> > > >
> > > > With Jan's permission, let's add:
> > > >
> > > > Reported-by: Jan Palus <jpalus@fastmail.com>
> > > >
> >
> > I was hoping to hear back, but I assume silence is kind of acceptance.
>
> I sent the reply with the tag after making sure off-list that Jan was OK
> with it. Sorry if that was not clear.
>
> > > Please don't do such (non-trivial) changes without making that clear
> > > in the commit message before your Signed-off-by tag:
> > >
> > > [ sudeep: rewrite commit message; switch to cleanup helpers ]
> > >
> >
> > Sorry I meant to do that when I replied and asked you if you are OK
> > with cleanup helpers. Also yes I planned to add a line like something
> > above before finalizing.
>
> Sounds like a mail has gotten lost since I never saw that question from
> you.
>
No I hadn't sent it yet, generally wait for builder report to finalise
the commit. Sometimes -next integration happens before build sends build
report for my branch and that happened this time.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-09-02 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 13:21 [PATCH] firmware: arm_scmi: quirk: fix write to string constant Johan Hovold
2025-08-29 14:29 ` Johan Hovold
2025-09-02 9:59 ` Johan Hovold
2025-09-02 10:16 ` Sudeep Holla
2025-09-02 10:27 ` Johan Hovold
2025-09-02 11:18 ` Sudeep Holla [this message]
2025-08-29 21:13 ` Cristian Marussi
2025-09-08 10:17 ` Sudeep Holla
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=20250902-original-hallowed-robin-d030bf@sudeepholla \
--to=sudeep.holla@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=johan@kernel.org \
--cc=jpalus@fastmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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