Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753920AbbK0EKx (ORCPT ); Thu, 26 Nov 2015 23:10:53 -0500 Received: from mail-pa0-f67.google.com ([209.85.220.67]:35954 "EHLO mail-pa0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753871AbbK0EKE (ORCPT ); Thu, 26 Nov 2015 23:10:04 -0500 From: Wenwei Tao To: mb@lightnvm.io, keith.busch@intel.com, axboe@fb.com Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, linux-nvme@lists.infradead.org Subject: [PATCH v2 0/3] fixes for LightNVM Date: Fri, 27 Nov 2015 12:09:41 +0800 Message-Id: <1448597384-27976-1-git-send-email-ww.tao0320@gmail.com> X-Mailer: git-send-email 1.8.3.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1320 Lines: 42 Hi Matias A couple of fixes based on 4.4rc2 Patch 1: the locking issue move codes 'register with device with a supported manager' into a funtion. But I think iterate over a list to register nvm device with a manger is not a good idea, since we can blocked in manager's register_mgr function while holding nvm_lock. Patch 2: handle targerts when underlying devices were removed free dev when exited call target type's exit function when target creation was aborted due to nvm device exit. Patch 3: change the interface between nvme and lightnvm remove the unnecessary nvme_ns->type set to zero Wenwei Tao (3): lightnvm: missing nvm_lock acquire lightnvm: handle targets when corresponding nvm device exit nvme: change the interface between nvme and lightnvm drivers/lightnvm/core.c | 197 ++++++++++++++++++++++++++----------------- drivers/nvme/host/lightnvm.c | 17 +++- drivers/nvme/host/nvme.h | 1 + drivers/nvme/host/pci.c | 7 +- include/linux/lightnvm.h | 3 + 5 files changed, 143 insertions(+), 82 deletions(-) -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/