linux-kernel - Re: [PATCH] msi: fix imbalanced refcount of msi irq sysfs objects

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+5PVA4-Xofs3AKq3L2UjtmVLa4HpjMwv0_rMdXO5ku8uFvfkg@mail.gmail.com>
Date:	Wed, 4 Jan 2012 16:25:47 -0500
From:	Josh Boyer <jwboyer@...il.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	David Miller <davem@...emloft.net>, nhorman@...driver.com,
	linux-kernel@...r.kernel.org, bhelgaas@...gle.com, gregkh@...e.de,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH] msi: fix imbalanced refcount of msi irq sysfs objects

On Wed, Jan 4, 2012 at 4:18 PM, Josh Boyer <jwboyer@...il.com> wrote:
>>> The bug only exists in the PCI -next code I thought.
>>
>> Oh yeah, looks like it.  Lost track of my -next vs master branches
>> there...
>
> Er... Neil's commit log in the patch itself has an oops from 3.1.6 in
> it.  If the bug the patch fixes is only present in -next PCI code, how
> did it get hit on that release?
>
> Did we switch to talking about some other patch here and I'm just confused?

I'm just confused.  I forgot Neil backported that upstream code to the
F16 3.1.6 kernel.  Sorry for the noise.

josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/