linux-kernel - Re: linux-next: Tree for Jan 25 (BROKEN suspend)

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130128192807.GF22465@mtj.dyndns.org>
Date:	Mon, 28 Jan 2013 11:28:07 -0800
From:	Tejun Heo <tj@...nel.org>
To:	Sedat Dilek <sedat.dilek@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Linux PM List <linux-pm@...ts.linux-foundation.org>,
	Linux ACPI <linux-acpi@...r.kernel.org>,
	Sasha Levin <sasha.levin@...cle.com>
Subject: Re: linux-next: Tree for Jan 25 (BROKEN suspend)

Hello, guys.

On Sun, Jan 27, 2013 at 02:01:50PM +0100, Sedat Dilek wrote:
> OK, that bisecting ruined a bit my weekend and showed me again you
> cannot really bisect Linux-Next.
> Sometimes, it is better not to trust the tools blindly and do a
> bisect-on-suspicion.
> Anyway... cultprit found... patch found... applied... all GOOD now.
> ( If I had waited for next Monday's next-20130127 I would not have
> seen what caused the trouble. ).

Yeah, my usual test setup didn't have async tasks w/o domain so I
failed to notice the breakage.  Sorry about the trouble guys and lots
of thanks to Sedat for the firefighting over the weekend.  :)

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