From: Pavel Machek <pavel@ucw.cz>
To: Jens Axboe <axboe@kernel.dk>,
jejb@linux.ibm.com, martin.petersen@oracle.com, lduncan@suse.com,
hare@suse.com, mcgrof@kernel.org, jthumshirn@suse.de, hch@lst.de,
gregkh@linuxfoundation.org, dan.j.williams@intel.com,
bvanassche@acm.org
Cc: kernel list <linux-kernel@vger.kernel.org>,
rjw@rjwysocki.net, linux-pm@vger.kernel.org,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
hdegoede@redhat.com, linux-ide@vger.kernel.org
Subject: regression -next -- scsi: sd: Rely on the driver core for asynchronous probing was Re: next-20190408..0418: Suspend/resume problems on Thinkpad X60
Date: Wed, 24 Apr 2019 22:48:32 +0200 [thread overview]
Message-ID: <20190424204832.GA3111@amd> (raw)
In-Reply-To: <20190424202119.GA26357@amd>
[-- Attachment #1.1: Type: text/plain, Size: 631 bytes --]
Hi!
> Not block, but it seems scsi subsystem is:
commit 21e6ba3f0e0257cce1a226c1f15e0a8ba4338ca3
Author: Bart Van Assche <bvanassche@acm.org>
Date: Wed Mar 20 13:09:19 2019 -0700
scsi: sd: Rely on the driver core for asynchronous probing
As explained during the 2018 LSF/MM session about increasing SCSI
disk
probing concurrency, the problems with the current probing
approach are as
Seems to be responsible. Full log attached.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: delme --]
[-- Type: text/plain, Size: 2458 bytes --]
# bad: [76c938fcaa4b4a5d8f05fa907925d5043834964e] Add linux-next specific files for 20190423
# good: [7142eaa58b49d9de492ccc16d48df7c488a5fbb6] Merge tag 'mips_fixes_5.1_3' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux
git bisect start 'next-20190423' '7142eaa58b49d9de492ccc16d48df7c488a5fbb6'
# good: [ed04f675fa2c22316d7b57bea1258a18a47537ea] Merge remote-tracking branch 'crypto/master'
git bisect good ed04f675fa2c22316d7b57bea1258a18a47537ea
# good: [4a99e5b3463f5c936540958914bff57ec50ac1e0] Merge remote-tracking branch 'spi/for-next'
git bisect good 4a99e5b3463f5c936540958914bff57ec50ac1e0
# good: [61cabbda2a7e966b689a6791050ad675e6dff274] Merge remote-tracking branch 'staging/staging-next'
git bisect good 61cabbda2a7e966b689a6791050ad675e6dff274
# bad: [c8f0c2453f64529035e25fbfb9de9d24e98baff7] Merge remote-tracking branch 'coresight/next'
git bisect bad c8f0c2453f64529035e25fbfb9de9d24e98baff7
# bad: [6fb251c6f174d3cc571391baa9f6e57fff505446] Merge branch 'misc' into for-next
git bisect bad 6fb251c6f174d3cc571391baa9f6e57fff505446
# bad: [78a8ab3cc0f95a66c8fb2429030289103de173e7] scsi: qedf: fixup bit operations
git bisect bad 78a8ab3cc0f95a66c8fb2429030289103de173e7
# good: [c0327e67ecd86e88f5bc5fd54bfdf9b422a1c93f] scsi: core: remove the scsi_ioctl_reset export
git bisect good c0327e67ecd86e88f5bc5fd54bfdf9b422a1c93f
# good: [cbb24e26735f6142ba994b4d44fc2dcd54c3fe1f] scsi: ufs-mediatek: Make some symbols static
git bisect good cbb24e26735f6142ba994b4d44fc2dcd54c3fe1f
# bad: [21e6ba3f0e0257cce1a226c1f15e0a8ba4338ca3] scsi: sd: Rely on the driver core for asynchronous probing
git bisect bad 21e6ba3f0e0257cce1a226c1f15e0a8ba4338ca3
# good: [e7f7b6f38a44697428f5a2e7c606de028df2b0e3] scsi: lpfc: change snprintf to scnprintf for possible overflow
git bisect good e7f7b6f38a44697428f5a2e7c606de028df2b0e3
# good: [3e14592da654d53d87987aa09753d5a26e45446f] scsi: gdth: Only call dma_free_coherent when buf is not NULL in ioc_general
git bisect good 3e14592da654d53d87987aa09753d5a26e45446f
# good: [8378573353728a02602d6f956a3df48db0505c65] scsi: libcxgbi: remove uninitialized variable len
git bisect good 8378573353728a02602d6f956a3df48db0505c65
# good: [ea9006dfda65b7dc369aaa2359b3dedfc1bb08b6] scsi: mpt3sas: fix indentation issue
git bisect good ea9006dfda65b7dc369aaa2359b3dedfc1bb08b6
# first bad commit: [21e6ba3f0e0257cce1a226c1f15e0a8ba4338ca3] scsi: sd: Rely on the driver core for asynchronous probing
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-04-24 20:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 17:39 next-20190408: Suspend/resume problems on Thinkpad X60 Pavel Machek
2019-04-12 10:28 ` Pavel Machek
2019-04-23 10:22 ` next-20190408..0418: " Pavel Machek
2019-04-23 13:55 ` Jens Axboe
2019-04-24 8:26 ` Pavel Machek
2019-04-24 9:54 ` Pavel Machek
2019-04-24 10:48 ` Pavel Machek
2019-04-24 20:21 ` Pavel Machek
2019-04-24 20:48 ` Pavel Machek [this message]
2019-04-24 20:51 ` regression -next -- scsi: sd: Rely on the driver core for asynchronous probing was " Pavel Machek
2019-04-24 20:56 ` Bart Van Assche
2019-04-25 7:33 ` Pavel Machek
2019-04-25 13:35 ` Bart Van Assche
2019-04-26 10:32 ` Pavel Machek
2019-04-26 14:58 ` Bart Van Assche
2019-04-26 17:59 ` Pavel Machek
2019-04-23 14:09 ` Bart Van Assche
2019-04-24 10:17 ` Pavel Machek
2019-04-24 22:34 ` Bart Van Assche
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=20190424204832.GA3111@amd \
--to=pavel@ucw.cz \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=hdegoede@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=jthumshirn@suse.de \
--cc=lduncan@suse.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mcgrof@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
/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).