From: Lukas Bulwahn <firstname.lastname@example.org>
To: Arnd Bergmann <email@example.com>
Cc: Michel Lespinasse <firstname.lastname@example.org>,
Davidlohr Bueso <email@example.com>,
Andrew Morton <firstname.lastname@example.org>,
Mete Polat <email@example.com>,
Jesper Nilsson <firstname.lastname@example.org>,
David Woodhouse <email@example.com>,
Ingo Molnar <firstname.lastname@example.org>,
Peter Zijlstra <email@example.com>,
Randy Dunlap <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>,
Geert Uytterhoeven <firstname.lastname@example.org>
Subject: Re: [PATCH] rbtree: remove unneeded explicit alignment in struct rb_node
Date: Thu, 5 Aug 2021 16:14:25 +0200 [thread overview]
Message-ID: <CAKXUXMxsx5V-ONCxaNaLd3mw_=Epca1eUg3SRsf3+QrTK07yXA@mail.gmail.com> (raw)
On Thu, Aug 5, 2021 at 4:02 PM Arnd Bergmann <email@example.com> wrote:
> On Thu, Aug 5, 2021 at 3:32 PM Lukas Bulwahn <firstname.lastname@example.org> wrote:
> > Commit e977145aeaad ("[RBTREE] Add explicit alignment to sizeof(long) for
> > struct rb_node.") adds an explicit alignment to the struct rb_node due to
> > some speciality of the CRIS architecture.
> > The support for the CRIS architecture was removed with commit c690eddc2f3b
> > ("CRIS: Drop support for the CRIS port")
> > So, remove this now unneeded explicit alignment in struct rb_node as well.
> > This basically reverts commit e977145aeaad ("[RBTREE] Add explicit
> > alignment to sizeof(long) for struct rb_node.").
> > Reported-by: Randy Dunlap <email@example.com>
> > Reported-by: Mete Polat <firstname.lastname@example.org>
> > Signed-off-by: Lukas Bulwahn <email@example.com>
> > ---
> > applies cleanly on next-20210804, but only x86 compile-checked.
> > Michel, Davidlohr, Jesper, David, please ack.
> > Mete, you might want to re-run your RBT test suite for this change.
> > Andrew, once acked, please pick this minor cleanup into your tree.
> Do you know why it needed the extra alignment on cris at the time?
I basically only know what David Woodhouse wrote in his commit message:
"... allegedly it was necessary for struct address_space on CRIS,
because it otherwise ended up being only byte-aligned."
> The revert would appear to change the alignment to 16 bits instead
> of 32 bits on m68k as well (not 8 bits as on cris), but I don't know if that
> can cause problems there.
I guess this patch would need to be exposed to testing on the various
architectures. I personally can only serve with testing x86 and maybe
with a bit of some arm architecture.
Should we CC the various architecture mailing lists and maintainers on
such a patch, or is that just noise for these maintainers?
Or could we just quickly pick this up into anyone's (Andrew's) tree
for linux-next and expose it to wider testing on other architectures
that way? If we see the patch cause failures (rbtree is widely used in
mm, fs, etc. and hence boot up would probably already fail), then we
know and we can adjust the comment with a patch v2 to know for the
future that this alignment is also relevant for other architectures.
next prev parent reply other threads:[~2021-08-05 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 13:32 [PATCH] rbtree: remove unneeded explicit alignment in struct rb_node Lukas Bulwahn
2021-08-05 14:02 ` Arnd Bergmann
2021-08-05 14:14 ` Lukas Bulwahn [this message]
2021-08-05 15:02 ` Davidlohr Bueso
2021-08-05 15:10 ` Peter Zijlstra
2021-08-05 17:20 ` Mete Polat
2021-08-06 8:52 ` Michel Lespinasse
2021-08-06 11:57 ` Peter Zijlstra
2021-08-10 22:46 ` Jesper Nilsson
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).