From: Balbir Singh <bsingharora@gmail.com>
To: Kees Cook <keescook@chromium.org>, Michael Ellerman <mpe@ellerman.id.au>
Cc: Breno Leitao <leitao@debian.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Laura Abbott <labbott@redhat.com>,
gromero@br.ibm.com,
Anshuman Khandual <khandual@linux.vnet.ibm.com>
Subject: Re: kernel BUG at mm/usercopy.c:72!
Date: Wed, 17 May 2017 20:05:16 +1000 [thread overview]
Message-ID: <1495015516.30802.9.camel@gmail.com> (raw)
In-Reply-To: <CAGXu5jK86RkgsWFdtSuGoZzuRZt4cqJcU4YSTjn=irv0Pbu3Rw@mail.gmail.com>
> > Kees, depending on how that turns out we may ask you to revert
> > 517e1fbeb65f ("mm/usercopy: Drop extra is_vmalloc_or_module() check").
>
> That's fine by me. Let me know what you think would be best.
>
> Laura, I don't see much harm in putting this back in place. It seems
> like it's just a matter of efficiency to have it removed?
It looks like we resolved struct page of 0xd000000003d80030 as PageSlab?
Balbir Singh.
next prev parent reply other threads:[~2017-05-17 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 19:19 kernel BUG at mm/usercopy.c:72! Breno Leitao
2017-05-16 4:00 ` Anshuman Khandual
2017-05-16 4:44 ` Balbir Singh
2017-05-16 5:04 ` Anshuman Khandual
2017-05-16 11:02 ` Michael Ellerman
2017-05-16 16:15 ` Breno Leitao
2017-05-16 11:09 ` Michael Ellerman
2017-05-16 14:32 ` Kees Cook
2017-05-16 14:35 ` Laura Abbott
2017-05-18 5:09 ` Michael Ellerman
2017-05-17 10:05 ` Balbir Singh [this message]
2017-05-18 10:16 ` Michael Ellerman
2017-05-18 10:58 ` Balbir Singh
2017-05-18 10:17 ` Michael Ellerman
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=1495015516.30802.9.camel@gmail.com \
--to=bsingharora@gmail.com \
--cc=gromero@br.ibm.com \
--cc=keescook@chromium.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=labbott@redhat.com \
--cc=leitao@debian.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).