From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753403AbbJOP50 (ORCPT ); Thu, 15 Oct 2015 11:57:26 -0400 Received: from mail-qk0-f171.google.com ([209.85.220.171]:33691 "EHLO mail-qk0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752237AbbJOP5Z (ORCPT ); Thu, 15 Oct 2015 11:57:25 -0400 From: j.glisse@gmail.com To: linux-kernel@vger.kernel.org Cc: =?UTF-8?q?J=C3=A9r=C3=B4me=20Glisse?= , , Haggai Eran , Sagi Grimberg , Shachar Raindel , Doug Ledford Subject: [PATCH] IB/core: Print error when umem fails due to locked memory limit. Date: Thu, 15 Oct 2015 10:21:56 -0400 Message-Id: <1444918916-17928-1-git-send-email-j.glisse@gmail.com> X-Mailer: git-send-email 1.8.3.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jérôme Glisse It can be rather tedious to find why userspace is failing when only thing kernel report is -ENOMEM. This add an error message so that user can figure out why they are getting -ENOMEM. Signed-off-by: Jérôme Glisse cc: Cc: Haggai Eran Cc: Sagi Grimberg Cc: Shachar Raindel Cc: Doug Ledford --- drivers/infiniband/core/umem.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/infiniband/core/umem.c b/drivers/infiniband/core/umem.c index 38acb3c..a66929e 100644 --- a/drivers/infiniband/core/umem.c +++ b/drivers/infiniband/core/umem.c @@ -169,6 +169,7 @@ struct ib_umem *ib_umem_get(struct ib_ucontext *context, unsigned long addr, lock_limit = rlimit(RLIMIT_MEMLOCK) >> PAGE_SHIFT; if ((locked > lock_limit) && !capable(CAP_IPC_LOCK)) { + pr_err("locked memory quota exhausted (see ulimit -l)\n"); ret = -ENOMEM; goto out; } -- 1.8.3.1