linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tao.Zeng <Tao.Zeng@amlogic.com>
To: Punit Agrawal <punit.agrawal@arm.com>
Cc: mgorman <mgorman@suse.de>, tglx <tglx@linutronix.de>,
	"dan.j.williams" <dan.j.williams@intel.com>,
	"nadav.amit" <nadav.amit@gmail.com>,
	khandual <khandual@linux.vnet.ibm.com>,
	"zi.yan" <zi.yan@cs.rutgers.edu>,
	n-horiguchi <n-horiguchi@ah.jp.nec.com>,
	"henry.willard" <henry.willard@oracle.com>,
	jglisse <jglisse@redhat.com>, linux-mm <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Re: Report A bug of PTE attribute set for mprotect
Date: Fri, 1 Jun 2018 09:32:12 +0800	[thread overview]
Message-ID: <2018060109321088618142@amlogic.com> (raw)
In-Reply-To: <87tvqn96ro.fsf@e105922-lin.cambridge.arm.com>

[-- Attachment #1: Type: text/plain, Size: 756 bytes --]

Dear Punit Agrawal:

Yes, I find kernel fixed int in:
http://10.8.9.5/kernel/common/commit/?h=amlogic-4.9-dev&id=e86f15ee64d8ee46255d964d55f74f5ba9af8c36

Thanks for your support!




Tao.Zeng

From: Punit Agrawal
Date: 2018-05-31 23:36
To: Tao.Zeng
CC: mgorman; tglx; dan.j.williams; nadav.amit; khandual; zi.yan; n-horiguchi; henry.willard; jglisse; linux-mm; linux-kernel
Subject: Re: Report A bug of PTE attribute set for mprotect
Tao.Zeng <Tao.Zeng@amlogic.com> writes:

[...]

> Background of this problem:

> Our kernel version is 3.14.29,

Are you able to reproduce the problem on a recent upstream kernel?

3.14.29 is more than three years old and the problem you see might have
been fixed since then.

Thanks,
Punit

[-- Attachment #2: Type: text/html, Size: 3550 bytes --]

      reply	other threads:[~2018-06-01  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 11:47 Tao.Zeng
2018-05-31 15:36 ` Punit Agrawal
2018-06-01  1:32   ` Tao.Zeng [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=2018060109321088618142@amlogic.com \
    --to=tao.zeng@amlogic.com \
    --cc=dan.j.williams@intel.com \
    --cc=henry.willard@oracle.com \
    --cc=jglisse@redhat.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=nadav.amit@gmail.com \
    --cc=punit.agrawal@arm.com \
    --cc=tglx@linutronix.de \
    --cc=zi.yan@cs.rutgers.edu \
    /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