Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760088AbdLRSa1 (ORCPT ); Mon, 18 Dec 2017 13:30:27 -0500 Received: from paleale.coelho.fi ([176.9.41.70]:51116 "EHLO farmhouse.coelho.fi" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1760072AbdLRSaU (ORCPT ); Mon, 18 Dec 2017 13:30:20 -0500 Message-ID: <1513621815.4827.430.camel@coelho.fi> From: Luca Coelho To: Paul Menzel , Johannes Berg , Emmanuel Grumbach , Intel Linux Wireless Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, it+linux-wireless@molgen.mpg.de Date: Mon, 18 Dec 2017 20:30:15 +0200 In-Reply-To: <1513175552.4827.365.camel@intel.com> References: <75bc638e-99a8-2f3f-6260-491f8a018af6@molgen.mpg.de> <1513175552.4827.365.camel@intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.2-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 91.156.4.241 X-SA-Exim-Mail-From: luca@coelho.fi Subject: Re: UBSAN: Undefined behaviour in drivers/net/wireless/intel/iwlwifi/mvm/utils.c:838:5 X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000) X-SA-Exim-Scanned: Yes (on farmhouse.coelho.fi) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1050 Lines: 38 On Wed, 2017-12-13 at 16:32 +0200, Luciano Coelho wrote: > On Wed, 2017-12-13 at 14:25 +0100, Paul Menzel wrote: > > Dear Linux folks, > > > > > > 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 Thanks! -- Cheers, Luca.