From: Thorsten Blum <thorsten.blum@linux.dev>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Oleg Nesterov <oleg@redhat.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Remove unnecessary zero-length struct member
Date: Thu, 17 Apr 2025 10:00:02 +0200 [thread overview]
Message-ID: <03F0731F-3C87-47D9-A739-01289873572B@linux.dev> (raw)
In-Reply-To: <alpine.DEB.2.21.2504160321210.23090@angie.orcam.me.uk>
On 16. Apr 2025, at 04:33, Maciej W. Rozycki wrote:
> On Fri, 11 Apr 2025, Thorsten Blum wrote:
>
>> Remove the zero-length struct member '__last' and use sizeof() to
>> calculate the value for MAX_REG_OFFSET.
>>
>> No functional changes intended.
>
> Have you verified that there's no change except for timestamp data in
> (non-debug) `vmlinux' produced with and w/o the patch applied?
>
> Also this is broken anyway: if you use MAX_REG_OFFSET for `offset' passed
> to `regs_get_register', then data past the end of `regs' will be accessed.
Yes, true. It seems like
if (unlikely(offset >= MAX_REG_OFFSET))
return 0;
should do the trick.
The comment also says "If @offset is bigger than MAX_REG_OFFSET", rather
than "is bigger than or equal to".
Happy to add it to v2 or a separate patch, if this is actually correct?!
Thanks,
Thorsten
next prev parent reply other threads:[~2025-04-17 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 9:00 [PATCH] MIPS: Remove unnecessary zero-length struct member Thorsten Blum
2025-04-16 2:33 ` Maciej W. Rozycki
2025-04-16 15:25 ` Thorsten Blum
2025-04-17 8:00 ` Thorsten Blum [this message]
2025-04-17 8:09 ` Maciej W. Rozycki
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=03F0731F-3C87-47D9-A739-01289873572B@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=oleg@redhat.com \
--cc=tsbogend@alpha.franken.de \
/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