From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752485AbcFALz1 (ORCPT <rfc822;w@1wt.eu>);
	Wed, 1 Jun 2016 07:55:27 -0400
Received: from ozlabs.org ([103.22.144.67]:54062 "EHLO ozlabs.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751037AbcFALz0 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 1 Jun 2016 07:55:26 -0400
Date: Wed, 1 Jun 2016 21:55:22 +1000
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michal Hocko <mhocko@kernel.org>
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
Message-ID: <20160601215522.31733a22@canb.auug.org.au>
In-Reply-To: <20160601085549.GI26601@dhcp22.suse.cz>
References: <20160601080209.GA7190@yexl-desktop>
	<20160601082457.GH26601@dhcp22.suse.cz>
	<20160601183748.6f72ca9c@canb.auug.org.au>
	<20160601085549.GI26601@dhcp22.suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Michal,

On Wed, 1 Jun 2016 10:55:49 +0200 Michal Hocko <mhocko@kernel.org> wrote:
>
> $ 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.

OK, that makes sense then.  But the "git show" error message could be a
bit better (something like "bad object", I guess).

> 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.

So when it hit Linus' tree, I would have removed it from my copy of
mmotm and, of course, its SHA will have changed since Andrew sends his
stuff as patches.

-- 
Cheers,
Stephen Rothwell