From: Song Liu <liu.song.a23@gmail.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm/mprotect: fix compilation warning because of unused 'mm' varaible
Date: Mon, 13 May 2019 16:51:12 -0400 [thread overview]
Message-ID: <CAPhsuW6fGS9OerFBYiyV=j_biQz6JGLoMm7mxzBf7mO9w1ZMEA@mail.gmail.com> (raw)
In-Reply-To: <1557305432-4940-1-git-send-email-rppt@linux.ibm.com>
On Wed, May 8, 2019 at 4:50 AM Mike Rapoport <rppt@linux.ibm.com> wrote:
>
> Since commit 0cbe3e26abe0 ("mm: update ptep_modify_prot_start/commit to
> take vm_area_struct as arg") the only place that uses the local 'mm'
> variable in change_pte_range() is the call to set_pte_at().
>
> Many architectures define set_pte_at() as macro that does not use the 'mm'
> parameter, which generates the following compilation warning:
>
> CC mm/mprotect.o
> mm/mprotect.c: In function 'change_pte_range':
> mm/mprotect.c:42:20: warning: unused variable 'mm' [-Wunused-variable]
> struct mm_struct *mm = vma->vm_mm;
> ^~
>
> Fix it by passing vma->mm to set_pte_at() and dropping the local 'mm'
> variable in change_pte_range().
>
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> mm/mprotect.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/mm/mprotect.c b/mm/mprotect.c
> index 028c724..61bfe24 100644
> --- a/mm/mprotect.c
> +++ b/mm/mprotect.c
> @@ -39,7 +39,6 @@ static unsigned long change_pte_range(struct vm_area_struct *vma, pmd_t *pmd,
> unsigned long addr, unsigned long end, pgprot_t newprot,
> int dirty_accountable, int prot_numa)
> {
> - struct mm_struct *mm = vma->vm_mm;
> pte_t *pte, oldpte;
> spinlock_t *ptl;
> unsigned long pages = 0;
> @@ -136,7 +135,7 @@ static unsigned long change_pte_range(struct vm_area_struct *vma, pmd_t *pmd,
> newpte = swp_entry_to_pte(entry);
> if (pte_swp_soft_dirty(oldpte))
> newpte = pte_swp_mksoft_dirty(newpte);
> - set_pte_at(mm, addr, pte, newpte);
> + set_pte_at(vma->mm, addr, pte, newpte);
This should be vma->vm_mm.
Thanks,
Song
>
> pages++;
> }
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-05-13 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:50 Mike Rapoport
2019-05-13 20:51 ` Song Liu [this message]
2019-05-13 20:54 ` Song Liu
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='CAPhsuW6fGS9OerFBYiyV=j_biQz6JGLoMm7mxzBf7mO9w1ZMEA@mail.gmail.com' \
--to=liu.song.a23@gmail.com \
--cc=akpm@linux-foundation.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