From: Meelis Roos <mroos@linux.ee>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-ia64@lists.kernel.org" <linux-ia64@lists.kernel.org>
Cc: "namit@vmware.com" <namit@vmware.com>,
"Hansen, Dave" <dave.hansen@intel.com>
Subject: Re: [bisected] "mm/vmalloc: Add flag for freeing of special permsissions" corrupts memory on ia64
Date: Mon, 8 Jul 2019 23:53:07 +0300 [thread overview]
Message-ID: <d09a4305-432a-0f7b-42b0-1eb57a4b374e@linux.ee> (raw)
In-Reply-To: <096ddb2cfbe83309396c48e75648889cae68e672.camel@intel.com>
> I am out of the office and don't have access to this hardware either. I
> will try to find someone at Intel that does to speed this up. In the
> meantime I can send you a logging patch to do some sanity checks if you
> are able to run it.
I am also cut off from testing anything - it seems the air conditioning
unit in my test site has failked for good now and the earliest I can test
anything is next week.
> I think I found your earlier mail, and it said 5.2-rc1 did not show the
> problem. I guess this wasn't the case after further testing, but 5.1
> continued to be problem free?
Yes, 5.2-rc1 was problematic in retesting, and 5.1 was OK.
I also started suspecting binutils upgrade meanwhile - I upgraded binutils
to 2.31.1-p5 in Gentoo right after booting into 5.1, but the bisection
results were finally consistent so I did not look into binutils versions
further. gcc has not changed for me recently.
--
Meelis Roos <mroos@linux.ee>
prev parent reply other threads:[~2019-07-08 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 9:53 Meelis Roos
2019-07-05 5:09 ` Edgecombe, Rick P
2019-07-08 20:53 ` Meelis Roos [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=d09a4305-432a-0f7b-42b0-1eb57a4b374e@linux.ee \
--to=mroos@linux.ee \
--cc=dave.hansen@intel.com \
--cc=linux-ia64@lists.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
/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
all inboxes | Powered by JetHome®