From: Igor Stoppa <igor.stoppa@huawei.com>
To: Jerome Glisse <jglisse@redhat.com>
Cc: Michal Hocko <mhocko@kernel.org>, Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Kees Cook <keescook@google.com>
Subject: Re: [RFC] Tagging of vmalloc pages for supporting the pmalloc allocator
Date: Wed, 9 Aug 2017 10:27:32 +0300 [thread overview]
Message-ID: <b83b980d-8adb-52ea-9b62-af33aff8f898@huawei.com> (raw)
In-Reply-To: <20170808231535.GA20840@redhat.com>
On 09/08/17 02:15, Jerome Glisse wrote:
> On Tue, Aug 08, 2017 at 03:59:36PM +0300, Igor Stoppa wrote:
[...]
>> I am tempted to add
>>
>> #define VM_PMALLOC 0x00000100
[...]
> VM_PMALLOC sounds fine to me also adding a comment there pointing to
> pmalloc documentation would be a good thing to do. The above are flags
> that are use only inside vmalloc context and so there is no issue
> here of conflicting with other potential user.
ok, will do
>>
>> Unless it's acceptable to check the private field in the page struct.
>> It would bear the pmalloc magic number.
>
> I thought you wanted to do:
> check struct page mapping field
> check vmap->flags for VM_PMALLOC
>
> bool is_pmalloc(unsigned long addr)
> {
> struct page *page;
> struct vm_struct *vm_struct;
>
> if (!is_vmalloc_addr(addr))
> return false;
> page = vmalloc_to_page(addr);
> if (!page)
> return false;
> if (page->mapping != pmalloc_magic_key)
page->private ?
I thought mapping would not work in the cases you mentioned?
> return false;
>
> vm_struct = find_vm_area(addr);
> if (!vm_struct)
> return false;
>
> return vm_struct->flags & VM_PMALLOC;
> }
>
> Did you change your plan ?
No, the code I have is almost 1:1 what you wrote.
Apart from mapping <=> private
In my previous mail I referred to page->private.
Maybe I was not very clear in what I wrote, but I'm almost 100% aligned
with your snippet.
>> I'm thinking to use a pointer to one of pmalloc data items, as signature.
>
> What ever is easier for you. Note that dereferencing such pointer before
> asserting this is really a pmalloc page would be hazardous.
Yes, it's not even needed in this scenario.
It was just a way to ensure that it would be a value that cannot be come
out accidentally as pointer value, since it is already taken.
--
igor
--
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-08-09 7:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 15:14 Igor Stoppa
2017-08-02 17:08 ` Jerome Glisse
2017-08-03 10:11 ` Igor Stoppa
2017-08-03 11:48 ` Michal Hocko
2017-08-03 12:20 ` Igor Stoppa
2017-08-03 13:55 ` Michal Hocko
2017-08-03 14:41 ` Igor Stoppa
2017-08-03 14:47 ` Jerome Glisse
2017-08-03 15:06 ` Igor Stoppa
2017-08-03 15:15 ` Michal Hocko
2017-08-04 8:02 ` Igor Stoppa
2017-08-04 8:12 ` Michal Hocko
2017-08-07 11:26 ` Igor Stoppa
2017-08-07 11:34 ` Michal Hocko
2017-08-07 13:31 ` Jerome Glisse
2017-08-07 14:13 ` Igor Stoppa
2017-08-07 19:12 ` Jerome Glisse
2017-08-08 12:59 ` Igor Stoppa
2017-08-08 23:15 ` Jerome Glisse
2017-08-09 7:27 ` Igor Stoppa [this message]
2017-08-10 7:14 ` Michal Hocko
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=b83b980d-8adb-52ea-9b62-af33aff8f898@huawei.com \
--to=igor.stoppa@huawei.com \
--cc=jglisse@redhat.com \
--cc=keescook@google.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhocko@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