[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1829163.dQHRSAV4G1@spock>
Date: Tue, 22 Jun 2021 19:26:31 +0200
From: Oleksandr Natalenko <oleksandr@...alenko.name>
To: Jan Kara <jack@...e.cz>
Cc: Paolo Valente <paolo.valente@...aro.org>,
Jens Axboe <axboe@...nel.dk>,
linux-block <linux-block@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Luca Mariotti <mariottiluca1@...mail.it>,
Holger Hoffstätte
<holger@...lied-asynchrony.com>,
Pietro Pedroni <pedroni.pietro.96@...il.com>,
Piotr Gorski <lucjan.lucjanov@...il.com>,
Khazhy Kumykov <khazhy@...gle.com>, Jan Kara <jack@...e.cz>
Subject: Re: [PATCH FIXES/IMPROVEMENTS 0/7] block, bfq: preserve control, boost throughput, fix bugs
Ahoj.
On úterý 22. června 2021 18:29:48 CEST Jan Kara wrote:
> On Tue 22-06-21 09:35:05, Oleksandr Natalenko wrote:
> > On úterý 22. června 2021 9:08:43 CEST Paolo Valente wrote:
> > > CCing also Jan and Khazhy, because in your commit log I see also the
> > > commit on bfq_requests_merged().
> > >
> > > Is this OOPS reproducible for you?
> >
> > No, I haven't found a reproducer, at least yet. It took half a day of
> > uptime to hit this, so might not be that easy.
>
> Hum, if you can acquire a crash dump it would be the easiest I guess. We'd
> need to find out more about the request we crash on - whether it's
> otherwise valid, in what state it is etc...
Yes, I understand that. Once (and if) I reproduce it reliably, of course.
Thanks.
--
Oleksandr Natalenko (post-factum)
Powered by blists - more mailing lists