From: Guenter Roeck <linux@roeck-us.net>
To: Christoph Hellwig <hch@lst.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: Linux 5.3-rc1
Date: Tue, 23 Jul 2019 07:58:05 -0700 [thread overview]
Message-ID: <20190723145805.GA5809@roeck-us.net> (raw)
In-Reply-To: <20190723054841.GA17148@lst.de>
On Tue, Jul 23, 2019 at 07:48:41AM +0200, Christoph Hellwig wrote:
> The fix was sent last morning my time:
>
> https://marc.info/?l=linux-scsi&m=156378725427719&w=2
Here is the updated bisect for the ppc scsi problem.
Guenter
---
# bad: [f65420df914a85e33b2c8b1cab310858b2abb7c0] Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
# good: [168c79971b4a7be7011e73bf488b740a8e1135c8] Merge tag 'kbuild-v5.3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild
git bisect start 'f65420df914a' '168c79971b4a'
# good: [106d45f350c7cac876844dc685845cba4ffdb70b] scsi: zfcp: fix request object use-after-free in send path causing wrong traces
git bisect good 106d45f350c7cac876844dc685845cba4ffdb70b
# bad: [bdd17bdef7d8da4d8eee254abb4c92d8a566bdc1] scsi: core: take the DMA max mapping size into account
git bisect bad bdd17bdef7d8da4d8eee254abb4c92d8a566bdc1
# good: [0cdc58580b37a160fac4b884266b8b7cb096f539] scsi: sd_zbc: Fix compilation warning
git bisect good 0cdc58580b37a160fac4b884266b8b7cb096f539
# bad: [7ad388d8e4c703980b7018b938cdeec58832d78d] scsi: core: add a host / host template field for the virt boundary
git bisect bad 7ad388d8e4c703980b7018b938cdeec58832d78d
# good: [f9b0530fa02e0c73f31a49ef743e8f44eb8e32cc] scsi: core: Fix race on creating sense cache
git bisect good f9b0530fa02e0c73f31a49ef743e8f44eb8e32cc
# first bad commit: [7ad388d8e4c703980b7018b938cdeec58832d78d] scsi: core: add a host / host template field for the virt boundary
next prev parent reply other threads:[~2019-07-23 14:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 21:33 Linux 5.3-rc1 Linus Torvalds
2019-07-21 22:55 ` Bhaskar Chowdhury
2019-07-22 22:21 ` Guenter Roeck
2019-07-22 23:45 ` James Bottomley
2019-07-23 2:42 ` Guenter Roeck
2019-07-23 5:28 ` James Bottomley
2019-07-23 14:25 ` Steffen Maier
2019-07-23 15:33 ` James Bottomley
2019-07-23 16:19 ` Guenter Roeck
2019-07-23 16:23 ` James Bottomley
2019-07-23 16:52 ` Guenter Roeck
2019-07-23 16:46 ` Steffen Maier
2019-07-23 5:48 ` Christoph Hellwig
2019-07-23 13:56 ` Guenter Roeck
2019-07-23 14:58 ` Guenter Roeck [this message]
2019-07-23 15:14 ` James Bottomley
2019-07-23 15:42 ` Guenter Roeck
2019-07-23 15:34 ` Christoph Hellwig
2019-07-23 15:40 ` Guenter Roeck
2019-07-23 16:18 ` Guenter Roeck
2019-07-25 11:17 ` linux-next: stats (Was: Linux 5.3-rc1) 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=20190723145805.GA5809@roeck-us.net \
--to=linux@roeck-us.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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