From: Pankaj Gupta <pagupta@redhat.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/madvise: reduce code duplication in error handling paths
Date: Thu, 1 Aug 2019 02:43:38 -0400 (EDT) [thread overview]
Message-ID: <1944499597.6210303.1564641818536.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1564640896-1210-1-git-send-email-rppt@linux.ibm.com>
>
> The madvise_behavior() function converts -ENOMEM to -EAGAIN in several
> places using identical code.
>
> Move that code to a common error handling path.
>
> No functional changes.
>
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> mm/madvise.c | 52 ++++++++++++++++------------------------------------
> 1 file changed, 16 insertions(+), 36 deletions(-)
>
> diff --git a/mm/madvise.c b/mm/madvise.c
> index 968df3a..55d78fd 100644
> --- a/mm/madvise.c
> +++ b/mm/madvise.c
> @@ -105,28 +105,14 @@ static long madvise_behavior(struct vm_area_struct
> *vma,
> case MADV_MERGEABLE:
> case MADV_UNMERGEABLE:
> error = ksm_madvise(vma, start, end, behavior, &new_flags);
> - if (error) {
> - /*
> - * madvise() returns EAGAIN if kernel resources, such as
> - * slab, are temporarily unavailable.
> - */
> - if (error == -ENOMEM)
> - error = -EAGAIN;
> - goto out;
> - }
> + if (error)
> + goto out_convert_errno;
> break;
> case MADV_HUGEPAGE:
> case MADV_NOHUGEPAGE:
> error = hugepage_madvise(vma, &new_flags, behavior);
> - if (error) {
> - /*
> - * madvise() returns EAGAIN if kernel resources, such as
> - * slab, are temporarily unavailable.
> - */
> - if (error == -ENOMEM)
> - error = -EAGAIN;
> - goto out;
> - }
> + if (error)
> + goto out_convert_errno;
> break;
> }
>
> @@ -152,15 +138,8 @@ static long madvise_behavior(struct vm_area_struct *vma,
> goto out;
> }
> error = __split_vma(mm, vma, start, 1);
> - if (error) {
> - /*
> - * madvise() returns EAGAIN if kernel resources, such as
> - * slab, are temporarily unavailable.
> - */
> - if (error == -ENOMEM)
> - error = -EAGAIN;
> - goto out;
> - }
> + if (error)
> + goto out_convert_errno;
> }
>
> if (end != vma->vm_end) {
> @@ -169,15 +148,8 @@ static long madvise_behavior(struct vm_area_struct *vma,
> goto out;
> }
> error = __split_vma(mm, vma, end, 0);
> - if (error) {
> - /*
> - * madvise() returns EAGAIN if kernel resources, such as
> - * slab, are temporarily unavailable.
> - */
> - if (error == -ENOMEM)
> - error = -EAGAIN;
> - goto out;
> - }
> + if (error)
> + goto out_convert_errno;
> }
>
> success:
> @@ -185,6 +157,14 @@ static long madvise_behavior(struct vm_area_struct *vma,
> * vm_flags is protected by the mmap_sem held in write mode.
> */
> vma->vm_flags = new_flags;
> +
> +out_convert_errno:
> + /*
> + * madvise() returns EAGAIN if kernel resources, such as
> + * slab, are temporarily unavailable.
> + */
> + if (error == -ENOMEM)
> + error = -EAGAIN;
> out:
> return error;
> }
looks good.
Acked-by: Pankaj Gupta <pagupta@redhat.com>
> --
> 2.7.4
>
>
next prev parent reply other threads:[~2019-08-01 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 6:28 [PATCH] mm/madvise: reduce code duplication in error handling paths Mike Rapoport
2019-08-01 6:43 ` Pankaj Gupta [this message]
2019-08-02 3:37 ` Anshuman Khandual
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1944499597.6210303.1564641818536.JavaMail.zimbra@redhat.com \
--to=pagupta@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).