From: Luca Coelho <luca@coelho.fi>
To: Paul Menzel <pmenzel+linux-wireless@molgen.mpg.de>,
sara.sharon@intel.com
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
it+linux-wireless@molgen.mpg.de,
Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>
Subject: Re: UBSAN: Undefined behaviour in drivers/net/wireless/intel/iwlwifi/mvm/utils.c:838:5
Date: Wed, 20 Dec 2017 13:44:34 +0200 [thread overview]
Message-ID: <1513770274.4827.482.camel@coelho.fi> (raw)
In-Reply-To: <a08aa1b3-9d75-2f38-a0f0-aefe181137da@molgen.mpg.de>
On Wed, 2017-12-20 at 12:00 +0100, Paul Menzel wrote:
> Dear Luca,
>
>
> Am 18.12.2017 um 19:30 schrieb Luca Coelho:
> > On Wed, 2017-12-13 at 16:32 +0200, Luciano Coelho wrote:
> > > On Wed, 2017-12-13 at 14:25 +0100, Paul Menzel wrote:
> > > > I enabled the undefined behavior sanitizer, and built Linus’
> > > > master branch under Ubuntu 17.10 with gcc (Ubuntu 7.2.0-
> > > > 8ubuntu3)
> > > > 7.2.0.
> > > >
> > > > ``` $ grep UBSAN /boot/config-4.15.0-rc3+
> > > > CONFIG_ARCH_HAS_UBSAN_SANITIZE_ALL=y #
> > > > CONFIG_ARCH_WANTS_UBSAN_NO_NULL is not set CONFIG_UBSAN=y
> > > > CONFIG_UBSAN_SANITIZE_ALL=y # CONFIG_UBSAN_ALIGNMENT is not
> > > > set
> > > > CONFIG_UBSAN_NULL=y ```
> > > >
> > > > Starting the system the messages below are printed.
> > > >
> > > > Starting the system and using the wireless device shows the
> > > > messages below.
> > >
> > > Thanks for reporting! This shouldn't cause any problems, but I'll
> > > fix it by checking that the mac80211_queue is not INVALID_QUEUE
> > > (255) which seems to be the trigger for this warning.
> >
> > Can you try the following patch to see if the problem goes away?
> >
> > http://pastebin.coelho.fi/7b624f474846da52.txt
>
> Thank you. The warning is gone now. Thank you.
Thanks for testing! We are actually improving the fix a bit, because it
seems that we should not have gotten INVALID_QUEUE there. We will have
a two-fold fix (Sari, whom I CCed, is working on the other patch).
> For the next time, it’d
> be great to provide the output of `git format-patch -1`, which can
> be
> applied with `git am`. The output of `git show` is with my knowledge
> hard to apply.
Ah, sorry about that. I didn't want to send a full patch here so that
it wouldn't get picked up by patchworks, so I just pastebinned it.
--
Luca.
next prev parent reply other threads:[~2017-12-20 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 13:25 Paul Menzel
2017-12-13 14:32 ` Luciano Coelho
2017-12-18 18:30 ` Luca Coelho
2017-12-20 11:00 ` Paul Menzel
2017-12-20 11:44 ` Luca Coelho [this message]
2017-12-21 10:38 ` Kalle Valo
2017-12-21 10:49 ` Paul Menzel
2017-12-21 10:57 ` Luca Coelho
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=1513770274.4827.482.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=emmanuel.grumbach@intel.com \
--cc=it+linux-wireless@molgen.mpg.de \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=pmenzel+linux-wireless@molgen.mpg.de \
--cc=sara.sharon@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
all inboxes | Powered by JetHome®