From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] missing ->mmap_sem around find_vma() in swp_emulate.c
Date: Thu, 20 Dec 2012 10:03:07 +0000 [thread overview]
Message-ID: <20121220100307.GZ14363@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <50D2BB23.5070105@gmail.com>
On Thu, Dec 20, 2012 at 08:15:47AM +0100, Dirk Behme wrote:
> Am 16.12.2012 01:25, schrieb Al Viro:
>> find_vma() is *not* safe when somebody else is removing vmas. Not just
>> the return value might get bogus just as you are getting it (this instance
>> doesn't try to dereference the resulting vma), the search itself can get
>> buggered in rather spectacular ways. IOW, ->mmap_sem really, really is
>> not optional here.
>>
>> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>> ---
>> diff --git a/arch/arm/kernel/swp_emulate.c b/arch/arm/kernel/swp_emulate.c
>> index df74518..ab1017b 100644
>> --- a/arch/arm/kernel/swp_emulate.c
>> +++ b/arch/arm/kernel/swp_emulate.c
>> @@ -109,10 +109,12 @@ static void set_segfault(struct pt_regs *regs, unsigned long addr)
>> {
>> siginfo_t info;
>>
>> + down_read(¤t->mm->mmap_sem);
>> if (find_vma(current->mm, addr) == NULL)
>> info.si_code = SEGV_MAPERR;
>> else
>> info.si_code = SEGV_ACCERR;
>> + up_read(¤t->mm->mmap_sem);
>>
>> info.si_signo = SIGSEGV;
>> info.si_errno = 0;
>
> Any comment on this?
Any comment required on this? No, it's from Al Viro, which means it's
(mostly) always correct. I'll look at merging it soon.
prev parent reply other threads:[~2012-12-20 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 0:25 [PATCH] missing ->mmap_sem around find_vma() in swp_emulate.c Al Viro
2012-12-20 7:15 ` Dirk Behme
2012-12-20 10:03 ` Russell King - ARM Linux [this message]
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=20121220100307.GZ14363@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).