linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Tejun Heo <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: at block/genhd.c:1574 disk_clear_events()
Date: Wed, 19 Dec 2012 11:01:47 -0500	[thread overview]
Message-ID: <50D1E4EB.6000200@oracle.com> (raw)
In-Reply-To: <20121219095632.GA27488@localhost>

On 12/19/2012 04:56 AM, Fengguang Wu wrote:
> Sasha,
> 
> However note that this warning does not show up in next-20121219.
> 
> Thanks,
> Fengguang
> 
> On Wed, Dec 19, 2012 at 05:52:41PM +0800, Fengguang Wu wrote:
>> Hi Sasha,
>>
>> I got the below warning and it's bisected to
>>
>> commit 42f8570f437b65aaf3ef176a38ad7d7fc5847d8b
>> Author: Sasha Levin <sasha.levin@oracle.com>
>> Date:   Mon Dec 17 10:01:23 2012 -0500
>>
>>     workqueue: use new hashtable implementation

Hi Fengguang,

I'm slightly confused here: afaik what you're testing is Linus's git HEAD, right? (I
got that from 3.7.0-01930-gbff6343).

Tejun stated that he queued that commit for 3.9, and indeed I don't see it in Linus's
master as of today.

Therefore, I'm not quite sure how you're hitting it in your bisection - the only place
that commit is supposed to be at is in Tejun's -next/linux-next trees.


Thanks,
Sasha

  reply	other threads:[~2012-12-19 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19  9:52 WARNING: at block/genhd.c:1574 disk_clear_events() Fengguang Wu
2012-12-19  9:56 ` Fengguang Wu
2012-12-19 16:01   ` Sasha Levin [this message]
2012-12-19 18:47     ` Tejun Heo
2012-12-19 19:27 ` [PATCH] workqueue: fix find_worker_executing_work() brekage from hashtable conversion Tejun Heo

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=50D1E4EB.6000200@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).