From mboxrd@z Thu Jan 1 00:00:00 1970 From: Colin Cross Subject: Re: [PATCH 1/2] freezer: add unsafe versions of freezable helpers Date: Mon, 6 May 2013 15:11:02 -0700 Message-ID: References: <1367615050-3894-1-git-send-email-ccross@android.com> <20130506065605.6e5ed5e2@tlielax.poochiereds.net> <20130506174336.447d0d75@tlielax.poochiereds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: Jeff Layton , lkml , Trond Myklebust , Len Brown , Pavel Machek , "Rafael J. Wysocki" , Peter Zijlstra , Ingo Molnar , "J. Bruce Fields" , "David S. Miller" , Andrew Morton , Mandeep Singh Baines , Paul Walmsley , Al Viro , "Eric W. Biederman" , Oleg Nesterov , linux-nfs , Linux PM list , netdev , Tejun Heo , Ben Chan , Steve French To: Linus Torvalds Return-path: In-Reply-To: Sender: linux-pm-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Mon, May 6, 2013 at 2:58 PM, Linus Torvalds wrote: > On Mon, May 6, 2013 at 2:54 PM, Colin Cross wrote: >>> >>> There are many other possibilities for other codepaths that end up in >>> wait_for_response(). Once we get a solution in place for NFS, we'll >>> need to do something very similar for CIFS. >> >> Makes sense, I will add CIFS to the patch. Would you prefer it in the >> same or separate patches. > > Quite frankly, is it worth resurrecting these patches at all? > > The only things it actually complained about are not worth the pain > fixing and are getting explicitly not warned about - is there any > reason to believe the patches are worth maintaining and the extra > complexity is worth it? There was at least one real other case caught when this patch was applied: https://lkml.org/lkml/2013/3/4/390. Tejun asked that I resurrect it because I'm adding some additional APIs similar to freezable_schedule() and he wanted to make sure they didn't get used improperly in the future.