From: Oleg Nesterov <oleg@redhat.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c
Date: Thu, 22 Jun 2017 22:51:15 +0200 [thread overview]
Message-ID: <20170622205115.GA4938@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1706221042550.20265@eggly.anvils>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
On 06/22, Hugh Dickins wrote:
>
> On Thu, 22 Jun 2017, Oleg Nesterov wrote:
> >
> > Something like the patch below? Yes, I thought about this too.
>
> Yes, that patch (times 11 for all the architectures)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Yes, yes, this is clear to me. But only after you have already explained
this in your previous email ;)
> But my own preference this morning is to do nothing, until we hear
> more complaints and can classify them as genuine userspace breakage,
> as opposed to testcases surprised by a new kernel implementation.
OK. Agreed. Lets wait for the "real" bug report.
FYI. I am still investigating that redhat internal bug report. And yes,
it was the real application. But. I still think that it fails by another
reason, just the test-case they provided doesn't match the reality and
it hits another (this) problem by accident.
Oleg.
WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Andrey Vagin <avagin@openvz.org>,
Pavel Emelyanov <xemul@virtuozzo.com>,
Dmitry Safonov <dsafonov@virtuozzo.com>,
Andrew Morton <akpm@linux-foundation.org>,
Adrian Reber <areber@redhat.com>, Michael Kerrisk <mtk@man7.org>,
Willy Tarreau <w@1wt.eu>,
kernel test robot <xiaolong.ye@intel.com>,
Michal Hocko <mhocko@suse.com>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>,
Larry Woodman <lwoodman@redhat.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c
Date: Thu, 22 Jun 2017 22:51:15 +0200 [thread overview]
Message-ID: <20170622205115.GA4938@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1706221042550.20265@eggly.anvils>
On 06/22, Hugh Dickins wrote:
>
> On Thu, 22 Jun 2017, Oleg Nesterov wrote:
> >
> > Something like the patch below? Yes, I thought about this too.
>
> Yes, that patch (times 11 for all the architectures)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Yes, yes, this is clear to me. But only after you have already explained
this in your previous email ;)
> But my own preference this morning is to do nothing, until we hear
> more complaints and can classify them as genuine userspace breakage,
> as opposed to testcases surprised by a new kernel implementation.
OK. Agreed. Lets wait for the "real" bug report.
FYI. I am still investigating that redhat internal bug report. And yes,
it was the real application. But. I still think that it fails by another
reason, just the test-case they provided doesn't match the reality and
it hits another (this) problem by accident.
Oleg.
next prev parent reply other threads:[~2017-06-22 20:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 2:35 [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c kernel test robot
2017-06-21 2:35 ` kernel test robot
2017-06-21 2:41 ` Hugh Dickins
2017-06-21 2:41 ` Hugh Dickins
2017-06-21 18:29 ` Linus Torvalds
2017-06-21 18:29 ` Linus Torvalds
2017-06-21 19:33 ` Oleg Nesterov
2017-06-21 19:33 ` Oleg Nesterov
2017-06-21 19:39 ` Linus Torvalds
2017-06-21 19:39 ` Linus Torvalds
2017-06-21 20:27 ` Oleg Nesterov
2017-06-21 20:27 ` Oleg Nesterov
2017-06-21 20:30 ` Linus Torvalds
2017-06-21 20:30 ` Linus Torvalds
2017-06-21 20:56 ` Oleg Nesterov
2017-06-21 20:56 ` Oleg Nesterov
2017-06-21 22:19 ` Linus Torvalds
2017-06-21 22:19 ` Linus Torvalds
2017-06-22 1:07 ` Hugh Dickins
2017-06-22 1:07 ` Hugh Dickins
2017-06-22 10:58 ` Dmitry Safonov
2017-06-22 10:58 ` Dmitry Safonov
2017-06-22 15:16 ` Oleg Nesterov
2017-06-22 15:16 ` Oleg Nesterov
2017-06-22 18:04 ` Hugh Dickins
2017-06-22 18:04 ` Hugh Dickins
2017-06-22 20:51 ` Oleg Nesterov [this message]
2017-06-22 20:51 ` Oleg Nesterov
2017-06-22 4:23 ` Hugh Dickins
2017-06-22 4:23 ` Hugh Dickins
2017-06-21 19:39 ` Hugh Dickins
2017-06-21 19:39 ` Hugh Dickins
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=20170622205115.GA4938@redhat.com \
--to=oleg@redhat.com \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.