Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759476AbbGHRrr (ORCPT ); Wed, 8 Jul 2015 13:47:47 -0400 Received: from smtp105.biz.mail.bf1.yahoo.com ([98.139.221.43]:28444 "EHLO smtp105.biz.mail.bf1.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758785AbbGHRro (ORCPT ); Wed, 8 Jul 2015 13:47:44 -0400 X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 755Oh4oVM1m9jJq.bwraTDJgTlnnjUNWmhS8YFpB7DyPOxK 8oaFh1GTJLrHhXIUMBbvQkBhdDRg9Kzgy8MtH1QhUSPgcG2aTcMQ9EPN7cSa Pyy6Y27AzfMv4UY6koUP14GwSOfQgmS3wCri7DW8GGEMc1yok6iEjATQf.6M dO1FFc8mI8TXJvuEozRAMuK0bzJH8vu37MENu2sf2cJ06ptSk4HfE0g0xCzf yafMs7ep7P3HwpRTf2C1NvG7sI2dbqlXiBjPaDQz107tOo6GED6NlanWazut t.aMQttGBgJP44IYXFe0.5WE8wJ4zinBDg7cEWEMFK0VrjjmUB5RZ6lZncL5 NGt7zuiSzpkPWk_Cyh8xpbt4qWmOW5rOnWPnmt3Ml3EzFWz9OwojNxf3obga CYqTBbh51krBPeqdjXglD3Nbyallysh3mRe.eyvfgkEox.vYeEYDbK1g5Klw Mg.D2oUotRvB0V8dRSIyafX5jxS1BFUEWNF1Q1sDVxFmN9M4fRsaU6WvIqnX evsEyRv8KPY3P8L4MbB6sEj0hGVMW0rJYsEsLiTBU7y0l1nQ- X-Yahoo-SMTP: OIJXglSswBDfgLtXluJ6wiAYv6_cnw-- Message-ID: <559D623D.405@schaufler-ca.com> Date: Wed, 08 Jul 2015 10:47:41 -0700 From: Casey Schaufler User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Linus Torvalds , Shuah Khan , Ming Lei , Greg Kroah-Hartman , SE Linux , william.c.roberts@intel.com CC: Linux Kernel Mailing List , Shuah Khan Subject: Re: Linux 4.2-rc1 References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1597 Lines: 47 On 7/8/2015 10:29 AM, Linus Torvalds wrote: > On Wed, Jul 8, 2015 at 10:17 AM, Linus Torvalds > wrote: >> Decoding the "Code:" line shows that this is the "->fw_id" dereference in >> >> if (add_uevent_var(env, "FIRMWARE=%s", fw_priv->buf->fw_id)) >> return -ENOMEM; >> >> and that "fw_priv->buf" pointer is NULL. >> >> However, I don't see anything that looks like it should have changed >> any of this since 4.1. > Looking at the otehr uses of "fw_priv->buf", they all check that > pointer for NULL. I see code like > > fw_buf = fw_priv->buf; > if (!fw_buf) > goto out; > > etc. > > Also, it looks like you need to hold the "fw_lock" to even look at > that pointer, since the buffer can get reallocated etc. > > So that uevent code really looks buggy. It just doesn't look like a > *new* bug to me. That code looks old, going back to 2012 and commit > 1244691c73b2. There have been SELinux changes to kernfs for 4.2. William, you might want to have a look here. > > Ming Lei? > > Linus > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/