From: Michal Hocko <mhocko@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: kernel test robot <xiaolong.ye@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp] [oom_reaper] df1e2f5663: EIP: [<81e30134>] mmput_async+0x9/0x6b SS:ESP 0068:819a5e78
Date: Wed, 1 Jun 2016 10:55:49 +0200 [thread overview]
Message-ID: <20160601085549.GI26601@dhcp22.suse.cz> (raw)
In-Reply-To: <20160601183748.6f72ca9c@canb.auug.org.au>
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@kernel.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
next prev parent reply other threads:[~2016-06-01 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 8:02 [lkp] [oom_reaper] df1e2f5663: EIP: [<81e30134>] mmput_async+0x9/0x6b SS:ESP 0068:819a5e78 kernel test robot
2016-06-01 8:24 ` Michal Hocko
2016-06-01 8:37 ` Stephen Rothwell
2016-06-01 8:55 ` Michal Hocko [this message]
2016-06-01 11:55 ` Stephen Rothwell
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=20160601085549.GI26601@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sfr@canb.auug.org.au \
--cc=xiaolong.ye@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