Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp629979imm; Wed, 18 Jul 2018 08:04:43 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcU8RvY2nGyoYbAZUTiwTtdOL8UTZPi4LkCCFCjH9nLhILzCDu3xSYvcl1vW2YLac5D4q2a X-Received: by 2002:a62:3ece:: with SMTP id y75-v6mr5602637pfj.7.1531926283912; Wed, 18 Jul 2018 08:04:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531926283; cv=none; d=google.com; s=arc-20160816; b=FjF1ojxxjpEgPhhRrtsETej5j+iRs3FNNmG+CXKswN8Cr77o7Vp/9SbFEcNlAgLzSp qkUvS7MBQ5ESSnpqmQfSh7dSyojCtXlV4sdsHLJxu489eQZJIVzZFY15KaXojMxBE/8P TU1HNEoMh+N4v+mTNDSMdsDxxcSLnJRX5C1SkM1KMHJABg4LuP7DiNuDXt9MXcFESrqn atK+4Dz5m1PPi8YYBNj/W05FPxYCRicwFDPhP81erwOnHzgLylTz91Bk5/KRUzhaWgIb 9l1YVyLWk6sulTeUA6G90hWI85GvyLftG5oQiB89qLonVQt/1mMs750XfsSTwpPhvT6U EnzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=eEQY/VXSBXh5gq6nXKoeFhNfVIBbTFHv5a/d+HlvnOI=; b=obw6UeinZ2lyCdgRSIwX/qmP63SiPVEGb4MWhORQrXSyFhx9r15CSNbrcjfUcq55J0 dBwYoWnWTOhU4NyyKnnzy7SPW1WmQWdG+yA6CPSaKbJz4I/sFMhDTHyjYzofDs0RKbrF 3TfiwTDDMg10JE2cinxWF4TfkscUk7r5juhP+m98vV/fNTs3kL9F+DRoFUurAQPnAXRg BwF8hfDKh/5PqWiWO7sBQrflpp+83RRAje75m8qofyWnoNVEgJ7808N0EjEPLM2mcC2U hOmsmCL7BZW4TzHHACmn9knnkHes3AFYyRYqGeh7sPwcl4qI8n6bdQbXzGKUdrDkVYUr Q6/Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y14-v6si3705804pgg.76.2018.07.18.08.04.28; Wed, 18 Jul 2018 08:04:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731198AbeGRPku (ORCPT + 99 others); Wed, 18 Jul 2018 11:40:50 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:58709 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726613AbeGRPku (ORCPT ); Wed, 18 Jul 2018 11:40:50 -0400 Received: from hsi-kbw-5-158-153-52.hsi19.kabel-badenwuerttemberg.de ([5.158.153.52] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1ffnyD-0008WD-ID; Wed, 18 Jul 2018 17:02:25 +0200 Date: Wed, 18 Jul 2018 17:02:22 +0200 (CEST) From: Thomas Gleixner To: Bjorn Helgaas cc: Paul Menzel , Bjorn Helgaas , linux-pci@vger.kernel.org, Linux Kernel Mailing List , Marc Zyngier Subject: Re: NULL pointer dereference in msi_set_mask_bit In-Reply-To: <20180718140636.GD128988@bhelgaas-glaptop.roam.corp.google.com> Message-ID: References: <20180718140636.GD128988@bhelgaas-glaptop.roam.corp.google.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 18 Jul 2018, Bjorn Helgaas wrote: > [+cc Marc, Thomas] Uurgh. That's definitely what I need right now ... :) > On Wed, Jul 18, 2018 at 03:28:15PM +0200, Paul Menzel wrote: > > > > 93.885: [ 23.020572] BUG: unable to handle kernel NULL pointer dereference at 000000000000003c > > 93.885: [ 23.029011] PGD 0 P4D 0 > > 93.885: [ 23.031670] Oops: 0000 [#1] SMP NOPTI > > 93.885: [ 23.035455] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.18.0-rc5+ #1 > > 93.885: [ 23.042079] Hardware name: MSI MS-7A37/B350M MORTAR (MS-7A37), BIOS 1.G1 05/17/2018 > > 93.886: [ 23.049868] RIP: 0010:msi_set_mask_bit+0xe/0x70 > > 93.913: [ 23.049868] Code: 00 53 48 89 fb e8 12 f8 ff ff 48 89 df 5b e9 c9 fe ff ff 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 53 48 8b 47 10 48 8b 58 10 43 3c 01 74 3c 8b 15 2e 85 21 01 31 c0 85 d2 75 25 8b 43 38 48 f6 43 3c 01 testb $0x1,0x3c(%rbx) That's: if (desc->msi_attrib.is_msix) > > 93.957: [ 23.049880] RSP: 0018:ffff9e8e5e803f78 EFLAGS: 00010046 > > 93.957: [ 23.049881] RAX: ffff9e8e45919000 RBX: 0000000000000000 RCX: 0000000000000000 > > 93.958: [ 23.049882] RDX: ffff9e8e45919000 RSI: 0000000000000001 RDI: ffff9e8e45919098 > > 93.958: [ 23.049882] RBP: ffff9e8e45919098 R08: 0000000000000000 R09: 0000000000000000 > > 93.958: [ 23.049882] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9e8e45919000 > > 93.958: [ 23.049883] R13: 0000000000000027 R14: 0000000000000000 R15: 0000000000000000 > > 93.959: [ 23.049884] FS: 0000000000000000(0000) GS:ffff9e8e5e800000(0000) knlGS:0000000000000000 > > 93.959: [ 23.049884] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > > 93.959: [ 23.049885] CR2: 000000000000003c CR3: 00000003fc5a4000 CR4: 00000000003406f0 > > 93.959: [ 23.049885] Call Trace: > > 93.959: [ 23.049887] > > 93.960: [ 23.049889] __irq_move_irq+0x3c/0x70 > > 93.960: [ 23.049892] apic_ack_irq+0x2b/0x30 > > 93.960: [ 23.049893] handle_edge_irq+0x7d/0x1d0 > > 93.960: [ 23.049895] handle_irq+0x1f/0x30 > > 93.960: [ 23.049898] do_IRQ+0x41/0xc0 > > 93.960: [ 23.049899] common_interrupt+0xf/0xf > > 93.961: [ 23.049900] and desc comes from irq_data->common->msi_desc I have no idea how that can happen for an MSI interrupt. Paul, is this reproducible? Thanks, tglx