From: Dmitry Safonov <dsafonov@virtuozzo.com>
To: linux-kernel@vger.kernel.org, mingo@redhat.com
Cc: 0x7f454c46@gmail.com, linux-mm@kvack.org, x86@kernel.org
Subject: Re: [PATCHv5 0/6] x86: 32-bit compatible C/R on x86_64
Date: Wed, 14 Sep 2016 18:56:10 +0300 [thread overview]
Message-ID: <28071a1b-5f2e-be74-0408-8ec0e26957db@virtuozzo.com> (raw)
In-Reply-To: <20160905133308.28234-1-dsafonov@virtuozzo.com>
On 09/05/2016 04:33 PM, Dmitry Safonov wrote:
> Changes from v4:
> - check both vm_ops and vm_private_data to avoid (unlikely) confusion
> with some other vma in map_vdso_once (as Andy noticed) - which would
> lead to unable to use this API in that unlikely-case
> (vm_private_data may be uninitialized and be the same as vvar_mapping
> or vdso_mapping pointer) - so I introduced one-liner helper
> vma_is_special_mapping().
>
> Changes from v3:
> - proper ifdefs around vdso_image_32
> - missed Reviewed-by tag
Ping?
It looks like, all acks are there and there are no objections.
--
Dmitry
--
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>
prev parent reply other threads:[~2016-09-14 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 13:33 Dmitry Safonov
2016-09-05 13:33 ` [PATCHv5 1/6] x86/vdso: unmap vdso blob on vvar mapping failure Dmitry Safonov
2016-09-05 13:33 ` [PATCHv5 2/6] x86/vdso: replace calculate_addr in map_vdso() with addr Dmitry Safonov
2016-09-05 13:33 ` [PATCHv5 3/6] x86/arch_prctl/vdso: add ARCH_MAP_VDSO_* Dmitry Safonov
2016-09-05 17:01 ` Andy Lutomirski
2016-09-05 13:33 ` [PATCHv5 4/6] x86/coredump: use pr_reg size, rather that TIF_IA32 flag Dmitry Safonov
2016-09-05 13:33 ` [PATCHv5 5/6] x86/ptrace: down with test_thread_flag(TIF_IA32) Dmitry Safonov
2016-09-05 13:33 ` [PATCHv5 6/6] x86/signal: add SA_{X32,IA32}_ABI sa_flags Dmitry Safonov
2016-09-14 15:56 ` Dmitry Safonov [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=28071a1b-5f2e-be74-0408-8ec0e26957db@virtuozzo.com \
--to=dsafonov@virtuozzo.com \
--cc=0x7f454c46@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=x86@kernel.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