From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f199.google.com (mail-pf0-f199.google.com [209.85.192.199]) by kanga.kvack.org (Postfix) with ESMTP id 0240F6B0005 for ; Mon, 25 Apr 2016 18:18:21 -0400 (EDT) Received: by mail-pf0-f199.google.com with SMTP id u190so394627961pfb.0 for ; Mon, 25 Apr 2016 15:18:20 -0700 (PDT) Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com. [2607:f8b0:400e:c00::22d]) by mx.google.com with ESMTPS id a141si366009pfa.80.2016.04.25.15.18.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Apr 2016 15:18:20 -0700 (PDT) Received: by mail-pf0-x22d.google.com with SMTP id y69so52259624pfb.1 for ; Mon, 25 Apr 2016 15:18:20 -0700 (PDT) Date: Mon, 25 Apr 2016 15:18:16 -0700 From: Yu Zhao Subject: Re: [PATCH] mm/zpool: use workqueue for zpool_destroy Message-ID: <20160425221816.GA1254@google.com> References: <1461619210-10057-1-git-send-email-ddstreet@ieee.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1461619210-10057-1-git-send-email-ddstreet@ieee.org> Sender: owner-linux-mm@kvack.org List-ID: To: Dan Streetman Cc: Andrew Morton , Seth Jennings , Sergey Senozhatsky , Minchan Kim , Nitin Gupta , Linux-MM , Sergey Senozhatsky , linux-kernel , Dan Streetman On Mon, Apr 25, 2016 at 05:20:10PM -0400, Dan Streetman wrote: > Add a work_struct to struct zpool, and change zpool_destroy_pool to > defer calling the pool implementation destroy. > > The zsmalloc pool destroy function, which is one of the zpool > implementations, may sleep during destruction of the pool. However > zswap, which uses zpool, may call zpool_destroy_pool from atomic > context. So we need to defer the call to the zpool implementation > to destroy the pool. > > This is essentially the same as Yu Zhao's proposed patch to zsmalloc, > but moved to zpool. Thanks, Dan. Sergey also mentioned another call path that triggers the same problem (BUG: scheduling while atomic): rcu_process_callbacks() __zswap_pool_release() zswap_pool_destroy() zswap_cpu_comp_destroy() cpu_notifier_register_begin() mutex_lock(&cpu_add_remove_lock); So I was thinking zswap_pool_destroy() might be done in workqueue in zswap.c. This way we fix both call paths. Or you have another patch to fix the second call path? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org