All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Valente <paolo.valente@linaro.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block <linux-block@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	linus.walleij@linaro.org, bfq-iosched@googlegroups.com,
	oleksandr@natalenko.name
Subject: Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge
Date: Mon, 7 May 2018 11:32:56 +0200	[thread overview]
Message-ID: <4299ECA6-4320-426E-B33A-F6CC1C1C5864@linaro.org> (raw)
In-Reply-To: <1525663384.5064.1.camel@gmx.de>



> Il giorno 07 mag 2018, alle ore 05:23, Mike Galbraith <efault@gmx.de> =
ha scritto:
>=20
> On Mon, 2018-05-07 at 04:43 +0200, Mike Galbraith wrote:
>> On Sun, 2018-05-06 at 09:42 +0200, Paolo Valente wrote:
>>>=20
>>> I've attached a compressed patch (to avoid possible corruption from =
my
>>> mailer).  I'm little confident, but no pain, no gain, right?
>>>=20
>>> If possible, apply this patch on top of the fix I proposed in this
>>> thread, just to eliminate possible further noise. Finally, the
>>> patch content follows.
>>>=20
>>> Hoping for a stroke of luck,
>>=20
>> FWIW, box didn't survive the first full build of the morning.
>=20
> Nor the second.
>=20

Great, finally the first good news!

Help from blk-mq experts would be fundamental here.  To increase the
chances to get it, I'm going to open a new thread on this.  In that
thread I'll ask you to provide an OOPS or something, I hope it is now
easier for you to get it.

Thanks,
Paolo

> 	-Mike

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Valente <paolo.valente@linaro.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block <linux-block@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	linus.walleij@linaro.org, bfq-iosched@googlegroups.com,
	oleksandr@natalenko.name
Subject: Re: [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge
Date: Mon, 7 May 2018 11:32:56 +0200	[thread overview]
Message-ID: <4299ECA6-4320-426E-B33A-F6CC1C1C5864@linaro.org> (raw)
In-Reply-To: <1525663384.5064.1.camel@gmx.de>



> Il giorno 07 mag 2018, alle ore 05:23, Mike Galbraith <efault@gmx.de> ha scritto:
> 
> On Mon, 2018-05-07 at 04:43 +0200, Mike Galbraith wrote:
>> On Sun, 2018-05-06 at 09:42 +0200, Paolo Valente wrote:
>>> 
>>> I've attached a compressed patch (to avoid possible corruption from my
>>> mailer).  I'm little confident, but no pain, no gain, right?
>>> 
>>> If possible, apply this patch on top of the fix I proposed in this
>>> thread, just to eliminate possible further noise. Finally, the
>>> patch content follows.
>>> 
>>> Hoping for a stroke of luck,
>> 
>> FWIW, box didn't survive the first full build of the morning.
> 
> Nor the second.
> 

Great, finally the first good news!

Help from blk-mq experts would be fundamental here.  To increase the
chances to get it, I'm going to open a new thread on this.  In that
thread I'll ask you to provide an OOPS or something, I hope it is now
easier for you to get it.

Thanks,
Paolo

> 	-Mike

  reply	other threads:[~2018-05-07  9:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 17:17 [PATCH BUGFIX] block, bfq: postpone rq preparation to insert or merge Paolo Valente
2018-05-04 19:46 ` Mike Galbraith
2018-05-05  8:19   ` Mike Galbraith
2018-05-05 10:39     ` Paolo Valente
2018-05-05 10:39       ` Paolo Valente
2018-05-05 14:56       ` Mike Galbraith
2018-05-05 14:56         ` Mike Galbraith
2018-05-06  7:42         ` Paolo Valente
2018-05-06  7:42           ` Paolo Valente
2018-05-07  2:43           ` Mike Galbraith
2018-05-07  2:43             ` Mike Galbraith
2018-05-07  3:23             ` Mike Galbraith
2018-05-07  3:23               ` Mike Galbraith
2018-05-07  9:32               ` Paolo Valente [this message]
2018-05-07  9:32                 ` Paolo Valente
2018-05-07  5:56           ` Mike Galbraith
2018-05-07  5:56             ` Mike Galbraith
2018-05-07  9:27             ` Paolo Valente
2018-05-07  9:27               ` Paolo Valente
2018-05-07 10:01               ` Mike Galbraith
2018-05-07 10:01                 ` Mike Galbraith
2018-05-07 18:03                 ` Paolo Valente
2018-05-07 18:03                   ` Paolo Valente
2018-05-06  7:33 ` Oleksandr Natalenko
2018-05-10 16:14 ` Bart Van Assche
2018-05-10 16:14   ` Bart Van Assche
2018-05-14 17:16   ` Paolo Valente
2018-05-14 17:16     ` Paolo Valente
2018-05-14 17:31     ` Jens Axboe
2018-05-14 17:37       ` Paolo Valente
2018-05-14 17:37         ` Paolo Valente

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=4299ECA6-4320-426E-B33A-F6CC1C1C5864@linaro.org \
    --to=paolo.valente@linaro.org \
    --cc=axboe@kernel.dk \
    --cc=bfq-iosched@googlegroups.com \
    --cc=broonie@kernel.org \
    --cc=efault@gmx.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr@natalenko.name \
    --cc=ulf.hansson@linaro.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.