From: Hugh Dickins <hughd@google.com>
To: Doug Smythies <dsmythies@telus.net>
Cc: Hugh Dickins <hughd@google.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Andrew Morton <akpm@linux-foundation.org>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
linux-mm@kvack.org
Subject: RE: ksmd lockup - kernel 4.11-rc series
Date: Thu, 6 Apr 2017 11:33:20 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.1704061127090.17094@eggly.anvils> (raw)
In-Reply-To: <000801d2aede$cc414cd0$64c3e670$@net>
On Thu, 6 Apr 2017, Doug Smythies wrote:
> Hi,
>
> Thank you for your quick work on this.
>
> On 2017.04.02 17:03 Hugh Dickins wrote:
> > On Tue, 28 Mar 2017, Hugh Dickins wrote:
> >> On Tue, 28 Mar 2017, Kirill A. Shutemov wrote:
> >>> On Mon, Mar 27, 2017 at 04:16:00PM -0700, Doug Smythies wrote:
>
> ...[snip]...
>
> > Worked out what it was yesterday, but my first patch failed overnight:
> > I'd missed the placement of the next_pte label. It had a similar fix
> > to mm/migrate.c in it, that hit me too in testing; but this morning I
> > find Naoya's 4b0ece6fa016 in git, which fixes that.
>
> I think I got that one sometimes also.
>
> > Same issue here.
> >
> > [PATCH] mm: fix page_vma_mapped_walk() for ksm pages
>
> ... [snip] ...
>
> To establish a baseline, I ran kernel 4.11-rc5 without this
> patch for 24 hours. The failure occurred twice.
>
> I have been running the exact same scenario with the patch
> for 55 hours now without any issues.
Great, thanks a lot for your careful testing and report.
>
> Note: I stayed with version 1 of the patch, even though there
> was a version 2 sent out on Monday.
Right, I'd have done the same once useful testing was under way:
that's fine, the fix is the same, but version 2 looks more elegant.
I guess Andrew can add
Tested-by: Doug Smythies <dsmythies@telus.net>
or replace the Reported-by tag by
Reported-and-Tested-by: Doug Smythies <dsmythies@telus.net>
I'm not sure which is in fashion at present.
Thanks!
Hugh
--
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-04-06 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 23:16 Doug Smythies
2017-03-27 23:36 ` Kirill A. Shutemov
2017-03-28 7:16 ` Hugh Dickins
2017-04-03 0:03 ` Hugh Dickins
2017-04-03 14:08 ` Kirill A. Shutemov
2017-04-03 18:08 ` Hugh Dickins
2017-04-03 19:37 ` Kirill A. Shutemov
2017-04-06 14:05 ` Doug Smythies
2017-04-06 18:33 ` Hugh Dickins [this message]
2017-03-28 6:05 ` Doug Smythies
2017-03-28 14:59 ` Doug Smythies
2017-03-28 15:39 ` Kirill A. Shutemov
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=alpine.LSU.2.11.1704061127090.17094@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=dsmythies@telus.net \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.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