From patchwork Fri Mar 11 15:29:05 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Charan Teja Kalla X-Patchwork-Id: 12778230 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9BDD9C433EF for ; Fri, 11 Mar 2022 15:31:09 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E7EAB8D0003; Fri, 11 Mar 2022 10:31:08 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id E2CEF8D0001; Fri, 11 Mar 2022 10:31:08 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D1BAB8D0003; Fri, 11 Mar 2022 10:31:08 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0137.hostedemail.com [216.40.44.137]) by kanga.kvack.org (Postfix) with ESMTP id C3C478D0001 for ; Fri, 11 Mar 2022 10:31:08 -0500 (EST) Received: from smtpin29.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 81C259F326 for ; Fri, 11 Mar 2022 15:31:08 +0000 (UTC) X-FDA: 79232493816.29.A595CFF Received: from alexa-out.qualcomm.com (alexa-out.qualcomm.com [129.46.98.28]) by imf02.hostedemail.com (Postfix) with ESMTP id 80AB680022 for ; Fri, 11 Mar 2022 15:31:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1647012667; x=1678548667; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=sxa44dfwh+7OfJVU2hGG661tCEMXjNsht7SbfX+FjMQ=; b=m9oFnRR8m9MCwDodx1GEkT4N4eRqxIM4pnZW9Gb9oreYDJylmZzgmVup kV07laFxjOBqiuaTmWEkSmybqZtujewfXgWrpXaJctlg5HDoPhHwFXqFN DUAQBQxzm8WP6RKSgeaXK+TsYRb+8NKfvZMmyk74ViprSwTrG/iY3b6m2 k=; Received: from ironmsg09-lv.qualcomm.com ([10.47.202.153]) by alexa-out.qualcomm.com with ESMTP; 11 Mar 2022 07:31:06 -0800 X-QCInternal: smtphost Received: from nasanex01c.na.qualcomm.com ([10.47.97.222]) by ironmsg09-lv.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Mar 2022 07:31:06 -0800 Received: from nalasex01a.na.qualcomm.com (10.47.209.196) by nasanex01c.na.qualcomm.com (10.47.97.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.15; Fri, 11 Mar 2022 07:31:05 -0800 Received: from hu-charante-hyd.qualcomm.com (10.80.80.8) by nalasex01a.na.qualcomm.com (10.47.209.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.15; Fri, 11 Mar 2022 07:31:01 -0800 From: Charan Teja Kalla To: , , , , , , , , CC: , , Charan Teja Kalla , "# 5 . 10+" Subject: [PATCH V2,1/2] mm: madvise: return correct bytes advised with process_madvise Date: Fri, 11 Mar 2022 20:59:05 +0530 Message-ID: <125b61a0edcee5c2db8658aed9d06a43a19ccafc.1647008754.git.quic_charante@quicinc.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: References: MIME-Version: 1.0 X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nalasex01a.na.qualcomm.com (10.47.209.196) X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: 80AB680022 X-Stat-Signature: i1ramo5fpbxn6cah74wtz57ggwibwqmq X-Rspam-User: Authentication-Results: imf02.hostedemail.com; dkim=pass header.d=quicinc.com header.s=qcdkim header.b=m9oFnRR8; spf=pass (imf02.hostedemail.com: domain of quic_charante@quicinc.com designates 129.46.98.28 as permitted sender) smtp.mailfrom=quic_charante@quicinc.com; dmarc=pass (policy=none) header.from=quicinc.com X-HE-Tag: 1647012667-238469 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: The process_madvise() system call returns error even after processing some VMA's passed in the 'struct iovec' vector list which leaves the user confused to know where to restart the advise next. It is also against this syscall man page[1] documentation where it mentions that "return value may be less than the total number of requested bytes, if an error occurred after some iovec elements were already processed.". Consider a user passed 10 VMA's in the 'struct iovec' vector list of which 9 are processed but one. Then it just returns the error caused on that failed VMA despite the first 9 VMA's processed, leaving the user confused about on which VMA it is failed. Returning the number of bytes processed here can help the user to know which VMA it is failed on and thus can retry/skip the advise on that VMA. [1]https://man7.org/linux/man-pages/man2/process_madvise.2.html. Fixes: ecb8ac8b1f14("mm/madvise: introduce process_madvise() syscall: an external memory hinting API") Cc: # 5.10+ Signed-off-by: Charan Teja Kalla Acked-by: Minchan Kim Acked-by: Michal Hocko --- Changes in V2: -- Separated the ENOMEM handling and return bytes processed, as per Minchan comments. -- This contains correcting return bytes processed with process_madvise(). Changes in V1: -- Fixed the ENOMEM handling and return bytes processed by process_madvise. -- https://patchwork.kernel.org/project/linux-mm/patch/1646803679-11433-1-git-send-email-quic_charante@quicinc.com/ mm/madvise.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/mm/madvise.c b/mm/madvise.c index 38d0f51..e97e6a9 100644 --- a/mm/madvise.c +++ b/mm/madvise.c @@ -1433,8 +1433,7 @@ SYSCALL_DEFINE5(process_madvise, int, pidfd, const struct iovec __user *, vec, iov_iter_advance(&iter, iovec.iov_len); } - if (ret == 0) - ret = total_len - iov_iter_count(&iter); + ret = (total_len - iov_iter_count(&iter)) ? : ret; release_mm: mmput(mm);