From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
John Garry <john.garry@huawei.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Julia Lawall <julia.lawall@inria.fr>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
nicolas.palix@univ-grenoble-alpes.fr,
linux-scsi <linux-scsi@vger.kernel.org>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Ming Lei <ming.lei@redhat.com>
Subject: Re: problem booting 5.10
Date: Tue, 8 Dec 2020 14:33:21 -0700 [thread overview]
Message-ID: <22f9a723-aaba-3a1b-b2bc-3f1d82840dd7@kernel.dk> (raw)
In-Reply-To: <CAHk-=wi=Xs6K7-Yj83yoGr=z5fTw+=MUHrLpFJZ0FOeHA2fjuA@mail.gmail.com>
On 12/8/20 2:25 PM, Linus Torvalds wrote:
> [ Just re-sending with Jens added back - he's been on a couple of the
> emails, but wean't on this one. Sorry for the duplication ]
Don't think I was, but gmail shows me the rest of the thread now.
> On Tue, Dec 8, 2020 at 1:23 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>>
>> On Tue, Dec 8, 2020 at 1:14 PM John Garry <john.garry@huawei.com> wrote:
>>>
>>> JFYI, About "scsi: megaraid_sas: Added support for shared host tagset
>>> for cpuhotplug", we did have an issue reported here already from Qian
>>> about a boot hang:
>>
>> Hmm. That does sound like it might be it.
>>
>> At this point, the patches from Ming Lei seem to be a riskier approach
>> than perhaps just reverting the megaraid_sas change?
>>
>> It looks like those patches are queued up for 5.11, and we could
>> re-apply the megaraid_sas change then?
>>
>> Jens, comments?
>>
>> And Julia - if it's that thing, then a
>>
>> git revert 103fbf8e4020
>>
>> would be the thing to test.
Ming's series is queued up for 5.11, so if the revert does show that
this is indeed the issue (and it sure looks like it), then I'd suggest
we simply revert this commit from 5.10 and we can revisit after the
merge window opens and Ming's patches are in anyway.
--
Jens Axboe
next prev parent reply other threads:[~2020-12-08 21:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.22.394.2012081813310.2680@hadrien>
2020-12-08 18:31 ` problem booting 5.10 Linus Torvalds
2020-12-08 18:37 ` Julia Lawall
2020-12-08 18:59 ` Martin K. Petersen
2020-12-08 19:19 ` Linus Torvalds
2020-12-08 19:29 ` Julia Lawall
2020-12-08 19:47 ` Linus Torvalds
2020-12-08 21:14 ` John Garry
2020-12-08 21:23 ` Linus Torvalds
2020-12-08 21:25 ` Linus Torvalds
2020-12-08 21:33 ` Jens Axboe [this message]
2020-12-08 22:40 ` Julia Lawall
2020-12-08 22:47 ` Jens Axboe
2020-12-08 22:52 ` Linus Torvalds
2020-12-08 22:53 ` Martin K. Petersen
2020-12-08 22:56 ` Linus Torvalds
2020-12-08 23:00 ` Jens Axboe
2020-12-08 23:00 ` Martin K. Petersen
2020-12-08 22:51 ` Martin K. Petersen
2020-12-08 23:13 ` John Garry
2020-12-09 8:21 ` Julia Lawall
2020-12-09 15:44 ` Julia Lawall
2020-12-09 15:51 ` John Garry
2020-12-09 18:50 ` Kashyap Desai
2020-12-09 16:47 ` Martin K. Petersen
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=22f9a723-aaba-3a1b-b2bc-3f1d82840dd7@kernel.dk \
--to=axboe@kernel.dk \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=julia.lawall@inria.fr \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=nicolas.palix@univ-grenoble-alpes.fr \
--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;
as well as URLs for NNTP newsgroup(s).