From: Dave Martin <Dave.Martin@arm.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <kees@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Brown <broonie@kernel.org>, Baoquan He <bhe@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
kexec@lists.infradead.org, binutils@sourceware.org,
devel@daynix.com
Subject: Re: [PATCH v3 5/6] s390/crash: Use note name macros
Date: Thu, 9 Jan 2025 12:08:04 +0000 [thread overview]
Message-ID: <Z3+8JGoiUyPFYGE8@e133380.arm.com> (raw)
In-Reply-To: <2ad7234d-bfc5-49e3-abe6-7a85d992329d@daynix.com>
Hi,
On Thu, Jan 09, 2025 at 02:29:19PM +0900, Akihiko Odaki wrote:
> On 2025/01/08 22:50, Dave Martin wrote:
> > On Wed, Jan 08, 2025 at 01:53:51PM +0900, Akihiko Odaki wrote:
> > > On 2025/01/08 1:17, Dave Martin wrote:
> > > > Hi,
> > > >
> > > > On Tue, Jan 07, 2025 at 09:45:56PM +0900, Akihiko Odaki wrote:
> > > > > Use note name macros to match with the userspace's expectation.
> > > > >
> > > > > Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> > > > > ---
> > > > > arch/s390/kernel/crash_dump.c | 62 ++++++++++++++++---------------------------
> > > > > 1 file changed, 23 insertions(+), 39 deletions(-)
> > > > >
> > > > > diff --git a/arch/s390/kernel/crash_dump.c b/arch/s390/kernel/crash_dump.c
> > > >
> > > > [...]
> >
> > > > > +#define NT_INIT(buf, type, desc) \
> > > > > + (nt_init_name((buf), NT_ ## type, &(desc), sizeof(desc), NN_ ## type))
> >
> > [...]
> >
> > > > (Note also, the outer parentheses and the parentheses around (buf)
> > > > appear redundant -- although harmless?)
> > >
> > > They only make a difference in trivial corner cases and may look needlessly
> > > verbose.
> >
> > (In case there was a misunderstanding here, I meant that some
> > parentheses can be removed without affecting correctness:
> >
> > #define NT_INIT(buf, type, desc) \
> > nt_init_name(buf, NT_ ## type, &(desc), sizeof(desc), NN_ ## type))
> >
> > It still doesn't matter though -- and some people do prefer to be
> > defensive anyway and err on the side of having too many parentheses
> > rather than too few.)
>
> Well, being very pedantic, there are some cases where these parentheses have
> some effect.
>
> If you omit the outer parentheses, the following code will have different
> consequences:
> a->NT_INIT(buf, PRSTATUS, desc)
>
> The parentheses around buf will make difference for the following code:
> #define COMMA ,
> NT_INIT(NULL COMMA buf, PRSTATUS, desc)
>
> But nobody will write such code.
Ah, it looks like you're right on both!
Apologies for the noise.
(I must try find a neat use for these...)
Cheers
---Dave
next prev parent reply other threads:[~2025-01-09 12:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 12:45 [PATCH v3 0/6] elf: Define " Akihiko Odaki
2025-01-07 12:45 ` [PATCH v3 1/6] " Akihiko Odaki
2025-01-07 12:45 ` [PATCH v3 2/6] binfmt_elf: Use " Akihiko Odaki
2025-01-07 16:18 ` Dave Martin
2025-01-08 4:34 ` Akihiko Odaki
2025-01-08 13:45 ` Dave Martin
2025-01-07 12:45 ` [PATCH v3 3/6] powwerpc: " Akihiko Odaki
2025-01-07 14:37 ` LEROY Christophe
2025-01-07 12:45 ` [PATCH v3 4/6] crash: " Akihiko Odaki
2025-01-07 12:45 ` [PATCH v3 5/6] s390/crash: " Akihiko Odaki
2025-01-07 16:17 ` Dave Martin
2025-01-08 4:53 ` Akihiko Odaki
2025-01-08 13:02 ` Heiko Carstens
2025-01-08 13:50 ` Dave Martin
2025-01-09 5:29 ` Akihiko Odaki
2025-01-09 12:08 ` Dave Martin [this message]
2025-01-07 12:45 ` [PATCH v3 6/6] crash: Remove KEXEC_CORE_NOTE_NAME Akihiko Odaki
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=Z3+8JGoiUyPFYGE8@e133380.arm.com \
--to=dave.martin@arm.com \
--cc=agordeev@linux.ibm.com \
--cc=akihiko.odaki@daynix.com \
--cc=bhe@redhat.com \
--cc=binutils@sourceware.org \
--cc=borntraeger@linux.ibm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devel@daynix.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kees@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=svens@linux.ibm.com \
--cc=vgoyal@redhat.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