From: Michal Hocko <mhocko@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: dan.j.williams@intel.com, akpm@linux-foundation.org,
borntraeger@de.ibm.com, dsterba@suse.com,
gregkh@linuxfoundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] mm: Release a semaphore in 'get_vaddr_frames()'
Date: Sun, 10 Dec 2017 10:45:45 +0100 [thread overview]
Message-ID: <20171210094545.GW20234@dhcp22.suse.cz> (raw)
In-Reply-To: <20171209070941.31828-1-christophe.jaillet@wanadoo.fr>
On Sat 09-12-17 08:09:41, Christophe JAILLET wrote:
> A semaphore is acquired before this check, so we must release it before
> leaving.
>
> Fixes: b7f0554a56f2 ("mm: fail get_vaddr_frames() for filesystem-dax mappings")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> -- Untested --
>
> The wording of the commit entry and log description could be improved
> but I didn't find something better.
The changelog is ok imo.
> ---
> mm/frame_vector.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/mm/frame_vector.c b/mm/frame_vector.c
> index 297c7238f7d4..e0c5e659fa82 100644
> --- a/mm/frame_vector.c
> +++ b/mm/frame_vector.c
> @@ -62,8 +62,10 @@ int get_vaddr_frames(unsigned long start, unsigned int nr_frames,
> * get_user_pages_longterm() and disallow it for filesystem-dax
> * mappings.
> */
> - if (vma_is_fsdax(vma))
> + if (vma_is_fsdax(vma)) {
> + up_read(&mm->mmap_sem);
> return -EOPNOTSUPP;
> + }
Is there any reason to do a different error handling than other error
paths? Namely not going without goto out?
>
> if (!(vma->vm_flags & (VM_IO | VM_PFNMAP))) {
> vec->got_ref = true;
> --
> 2.14.1
>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-10 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 7:09 Christophe JAILLET
2017-12-10 9:45 ` Michal Hocko [this message]
2017-12-11 7:28 ` Christophe JAILLET
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=20171210094545.GW20234@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dan.j.williams@intel.com \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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