linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kvalo@kernel.org>, kernel test robot <lkp@intel.com>,
	kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-wireless@vger.kernel.org
Subject: Re: [linux-next:master 3615/4301] include/linux/compiler_types.h:335:45: error: call to '__compiletime_assert_314' declared with attribute error: BUILD_BUG_ON failed: sizeof(txpd->tx_dest_addr) != ETH_ALEN
Date: Wed, 1 Dec 2021 11:04:25 -0800	[thread overview]
Message-ID: <202112011059.1F60C79D@keescook> (raw)
In-Reply-To: <17ccfc4f9f9e74e1d6b48366a87cbcf887521dab.camel@sipsolutions.net>

On Wed, Dec 01, 2021 at 06:29:49PM +0100, Johannes Berg wrote:
> On Wed, 2021-12-01 at 08:41 -0800, Kees Cook wrote:
> > 
> > > >    drivers/net/wireless/marvell/libertas/tx.c:116:9: note: in expansion of macro 'BUILD_BUG_ON'
> > > >      116 |         BUILD_BUG_ON(sizeof(txpd->tx_dest_addr) != ETH_ALEN);
> > > >          |         ^~~~~~~~~~~~
> > > 
> > > Kees, can you take a look at this build error? You added the
> > > BUILD_BUG_ON(), right?
> > 
> > I will investigate! Given this doesn't happen on allmodconfig but
> > a randconfig trips it, this might be finding a legit issue, but I'll
> > report back more details.
> > 
> 
> It's probably some alignment thing - note it happened on a specific ARM
> with a specific compiler?

Yup, that was it. It's an interesting bit of "accidentally correct"
problems that I think I've now fixed with this series:
https://lore.kernel.org/all/20211201173234.578124-1-keescook@chromium.org/

My pahole before/after testing appears to have been too limited and
missed this case. :( I'm currently reviewing all the others I've sent as
well.

> But there's not really a good reason to even have the struct_group here,
> we only use it as if it was
> 
> 	u8 tx_dest_addr[ETH_ALEN];
> 
> anyway?

Ah yeah, nothing uses tx_dest_addr_high nor tx_dest_addr_low. Should I
send another patch to just rip out the struct_group entirely?

-- 
Kees Cook


  reply	other threads:[~2021-12-01 19:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 13:21 kernel test robot
2021-12-01  7:43 ` Kalle Valo
2021-12-01 16:41   ` Kees Cook
2021-12-01 17:29     ` Johannes Berg
2021-12-01 19:04       ` Kees Cook [this message]
2021-12-01 19:37         ` Johannes Berg

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=202112011059.1F60C79D@keescook \
    --to=keescook@chromium.org \
    --cc=johannes@sipsolutions.net \
    --cc=kbuild-all@lists.01.org \
    --cc=kvalo@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.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