[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160601085549.GI26601@dhcp22.suse.cz>
Date: Wed, 1 Jun 2016 10:55:49 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: kernel test robot <xiaolong.ye@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
LKML <linux-kernel@...r.kernel.org>, lkp@...org
Subject: Re: [lkp] [oom_reaper] df1e2f5663: EIP: [<81e30134>]
mmput_async+0x9/0x6b SS:ESP 0068:819a5e78
On Wed 01-06-16 18:37:48, Stephen Rothwell wrote:
> Hi Michal,
>
> On Wed, 1 Jun 2016 10:24:58 +0200 Michal Hocko <mhocko@...nel.org> wrote:
> >
> > $ git describe next/master
> > next-20160601
> > $ git show df1e2f56632ddf17186f7036a3bd809d3aed8fd8:mm/oom_kill.c
> > fatal: Path 'mm/oom_kill.c' exists on disk, but not in 'df1e2f56632ddf17186f7036a3bd809d3aed8fd8'
>
> That's weird:
$ git show df1e2f56632ddf17186f7036a3bd809d3aed8fd8
fatal: bad object df1e2f56632ddf17186f7036a3bd809d3aed8fd8
But a collegue of mine has it and
$ git describe --contains df1e2f56632ddf17186f7036a3bd809d3aed8fd8
next-20160527~2^2~53
But my tree doesn't seem to have this tag
$ git show next-20160527
fatal: ambiguous argument 'next-20160527': unknown revision or path not in the working tree.
So it seemed to be in linux-next but it is not in next-20160601. It is
in the Linus tree as e2fe14564d33 ("oom_reaper: close race with exiting
task") reachable from next-20160527.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists