Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753253AbdLMOcj (ORCPT ); Wed, 13 Dec 2017 09:32:39 -0500 Received: from mga14.intel.com ([192.55.52.115]:3668 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752864AbdLMOcg (ORCPT ); Wed, 13 Dec 2017 09:32:36 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,397,1508828400"; d="scan'208";a="15660161" Message-ID: <1513175552.4827.365.camel@intel.com> Subject: Re: UBSAN: Undefined behaviour in drivers/net/wireless/intel/iwlwifi/mvm/utils.c:838:5 From: Luciano 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: Wed, 13 Dec 2017 16:32:32 +0200 In-Reply-To: <75bc638e-99a8-2f3f-6260-491f8a018af6@molgen.mpg.de> References: <75bc638e-99a8-2f3f-6260-491f8a018af6@molgen.mpg.de> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.2-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 812 Lines: 29 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. -- Cheers, Luca.