From: Greg KH <gregkh@linuxfoundation.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Huang Pei <huangpei@loongson.cn>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Sasha Levin <sashal@kernel.org>, Christoph Hellwig <hch@lst.de>,
stable@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>
Subject: Re: [BUG] new MIPS compile error on v5.15.27
Date: Thu, 10 Mar 2022 20:05:04 +0100 [thread overview]
Message-ID: <YipL4KYG0hXa0g2s@kroah.com> (raw)
In-Reply-To: <D148EFBD-55E0-449A-AD2A-12C80ABD4FC4@goldelico.com>
On Thu, Mar 10, 2022 at 05:25:07PM +0100, H. Nikolaus Schaller wrote:
> upstream commit 277c8cb3e8ac ("MIPS: fix local_{add,sub}_return on MIPS64")
>
> was backported to v5.15.27 as
>
> commit f98371d2ac83 ("MIPS: fix local_{add,sub}_return on MIPS64")
>
> but breaks MIPS build:
>
> In file included from ./arch/mips/include/asm/local.h:8:0,
> from ./include/linux/genhd.h:20,
> from ./include/linux/blkdev.h:8,
> from ./include/linux/blk-cgroup.h:23,
> from ./include/linux/writeback.h:14,
> from ./include/linux/memcontrol.h:22,
> from ./include/net/sock.h:53,
> from ./include/linux/tcp.h:19,
> from drivers/net/slip/slip.c:91:
> ./arch/mips/include/asm/asm.h:68:0: warning: "END" redefined
> #define END(function) \
>
> In file included from drivers/net/slip/slip.c:88:0:
> drivers/net/slip/slip.h:44:0: note: this is the location of the previous definition
> #define END 0300 /* indicates end of frame */
>
> Analyses reveals that with the backported MIPS fix there is a new
> #include <asm/asm.h> introduced by ./arch/mips/include/asm/local.h
> which already defines some END macro.
>
> But why does v5.16.x compile fine where
>
> commit a0ecfd10d669c ("MIPS: fix local_{add,sub}_return on MIPS64")
>
> is also present since v5.16.3?
>
> Deeper analyses shows that there is another patch introduced
> in v5.16-rc1 which removed one #include in the above chain and
> therefore does not define END by asm/asm.h:
>
> commit 348332e000697 ("mm: don't include <linux/blk-cgroup.h> in <linux/writeback.h>")
>
> Hence, the MIPS fix should only be applied to branches where
> the mm fix is already present. Or the mm fix should be backported
> as well (if it has no side-effects).
>
> Note: the MIPS fix was apparently not (yet?) applied to v5.10.y or earlier
> even tough the Fixes: 7232311ef14c ("local_t: mips extension")
> would be true.
Thanks for the report. I'll work on resolving this for the next round
of stable releases _after_ the ones that are currently out for review
are released.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-10 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 16:25 [BUG] new MIPS compile error on v5.15.27 H. Nikolaus Schaller
2022-03-10 16:28 ` Christoph Hellwig
2022-03-10 16:34 ` H. Nikolaus Schaller
2022-03-10 16:39 ` H. Nikolaus Schaller
2022-03-10 16:48 ` Maciej W. Rozycki
2022-03-10 19:05 ` Greg KH [this message]
2022-03-10 19:26 ` Christoph Hellwig
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=YipL4KYG0hXa0g2s@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=hns@goldelico.com \
--cc=huangpei@loongson.cn \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).