linux-kernel - Re: [PATCH v3 0/2] nfs/sunrpc: allow freezing of tasks with NFS calls in flight

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: <201111282207.07098.rjw@sisk.pl>
Date:	Mon, 28 Nov 2011 22:07:06 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Tejun Heo <tj@...nel.org>
Cc:	Jeff Layton <jlayton@...hat.com>, linux-kernel@...r.kernel.org,
	linux-nfs@...r.kernel.org, linux-pm@...r.kernel.org,
	john@...va.com, trond.myklebust@...app.com,
	marek.belisko@...il.com, awilliam@...hat.com
Subject: Re: [PATCH v3 0/2] nfs/sunrpc: allow freezing of tasks with NFS calls in flight

On Monday, November 28, 2011, Tejun Heo wrote:
> On Mon, Nov 28, 2011 at 09:22:53PM +0100, Rafael J. Wysocki wrote:
> > If no one objects, I'll take these patches to linux-pm/linux-next in the
> > next couple of days (and then to the pm-freezer branch, if there are no
> > visible problems with them).
> 
> Rafael, I think these need to be routed through pm-freezer branch.
> Freezer went through a lot of changes and I don't think this will work
> reliably without the freezer changes.

The linux-next branch contains pm-freezer (or at least it's supposed to).

The point is to let the patches stay in linux-next for a couple of days
before moving them to the pm-freezer branch to see if there's any fallout (I'm
not going to rebase pm-freezer, so fixing it will require addtional commits).

Thanks,
Rafael
--
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/