linux-kernel - longterm backport request: xen/timer: Missing IRQF_NO

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 17 Oct 2011 10:32:24 +0100
From:	Ian Campbell <Ian.Campbell@...rix.com>
To:	Greg KH <greg@...ah.com>, "stable@...nel.org" <stable@...nel.org>
CC:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: longterm backport request: xen/timer: Missing IRQF_NO_SUSPEND in
 timer code broke suspend

(resending since I suspect stable@ was down the first time round. Also I
should have CC'd Thomas & LKML, I think)

Hi Greg,

Please can you queue this commit for 3.6.32.y

        commit f611f2da99420abc973c32cdbddbf5c365d0a20c
        Author: Ian Campbell <Ian.Campbell@...rix.com>
        Date:   Tue Feb 8 14:03:31 2011 +0000
        
            xen/timer: Missing IRQF_NO_SUSPEND in timer code broke suspend.
            
            The patches missed an indirect use of IRQF_NO_SUSPEND pulled in via
            IRQF_TIMER. The following patch fixes the issue.
            
            With this fixlet PV guest migration works just fine. I also booted the
            entire series as a dom0 kernel and it appeared fine.
            
            Signed-off-by: Ian Campbell <ian.campbell@...rix.com>
            Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>

It is needed in any tree which contains 676dc3cf5bc3 "xen: Use
IRQF_FORCE_RESUME" but not this change (everything was fixed upstream in
2.6.39-rc1).

It's a bit hard to tell in the absence of kernel.org but I have an old
(but post February) checkout of the 2.6.35 longterm and it does not appear
to have the original problematic patch so the fix isn't needed there.
IOW AFAICT right now 2.6.32 seems to be the only relevant tree.

Thanks,
Ian.



--
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/