From: "George Spelvin" <linux@horizon.com>
To: nab@kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org, linux@horizon.com,
linux-scsi@vger.kernel.org
Subject: Re: [Bug 19642] 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113
Date: 4 Oct 2010 21:24:23 -0400 [thread overview]
Message-ID: <20101005012423.31548.qmail@science.horizon.com> (raw)
In-Reply-To: <1286237419.18417.306.camel@haakon2.linux-iscsi.org>
> Would you be able to 'git bisect' on your system with Linus'es
> linux-2.6.git tree from commit 9fe6206f400646a (v2.6.35) to HEAD at
> v2.6.36-rc6 to help us pinpoint which commit the breakage was
> introduced..?
It's tedious, but I can, HOWEVER...
any advice avoiding false positives from
https://bugzilla.kernel.org/show_bug.cgi?id=16275
introduced in 74450be123b6f3cb480c358a056be398cce6aa6e
and fixed in 2c7d46ec192e4f2b350f67a0e185b9bce646cd6b?
I suppose I could cherry-pick the latter when in the
vulnerable range...
next prev parent reply other threads:[~2010-10-05 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101005000309.8466.qmail@science.horizon.com>
2010-10-05 0:10 ` [Bug 19642] 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113 Nicholas A. Bellinger
2010-10-05 0:18 ` Nicholas A. Bellinger
2010-10-05 1:24 ` George Spelvin [this message]
2010-10-03 21:15 2.6.36-rc6-git2: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-10-03 21:19 ` [Bug #19642] 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113 Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2010-10-03 18:37 [Bug 19642] New: " bugzilla-daemon
2010-10-03 18:37 ` [Bug 19642] " bugzilla-daemon
2010-10-03 18:54 ` bugzilla-daemon
2010-10-03 21:32 ` bugzilla-daemon
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=20101005012423.31548.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@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 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.