public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] Block fixes for 4.17-rc2
Date: Wed, 25 Apr 2018 11:06:04 -0600	[thread overview]
Message-ID: <96816828-4521-0bab-df73-1e2ecddd7f77@kernel.dk> (raw)
In-Reply-To: <E045C6CF-0E1E-44DB-B82B-43932F76A327@linaro.org>

On 4/25/18 11:03 AM, Paolo Valente wrote:
> 
> 
>> Il giorno 25 apr 2018, alle ore 18:50, Jens Axboe <axboe@kernel.dk> ha scritto:
>>
>> Hi Linus,
>>
>> I ended up sitting on this about a week longer than I wanted to,
>> since we were hashing out details with a timeout change. I've now
>> killed that patch, so we can flush the existing queue in due time.
>>
>> This pull request contains:
>>
>> - Fix for an old regression, where entering the queue can be disturbed
>>  by a signal to the process. This can cause spurious EIO. Fix from Alan
>>  Jenkins.
>>
>> - cdrom information leak fix from Dan.
>>
>> - Trivial helper for testing queue FUA from Dave Chinner, part of his
>>  O_DIRECT FUA series.
>>
>> - Series of swim fixes from Finn that actually makes it work again.
>>
>> - Loop O_DIRECT corruption fix, which caused data corruption in
>>  production for us. From me.
>>
>> - BFQ crash fix from me.
>>
> 
> For what it's worth, I disagree with this patch.  This change is based
> on an apparently buggy motivation, as I wrote in my reply in the
> thread where Jens proposed it.  As such, I think it might even bury
> more deeply the actual bug that causes the crash (although of course
> this patch does eliminate the crash for the use case reported in that
> thread).

The patch fixes the issue and I've explained why. If you have a
motivation to fix it differently, for whatever reason, then by all
means submit a patch. So far I haven't seen it, and we still have
the known crash that people are actually hitting.

I'll be happy to work with you on that later in the week, when
the LSFMM conference has wound down.

-- 
Jens Axboe

  reply	other threads:[~2018-04-25 17:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 16:50 [GIT PULL] Block fixes for 4.17-rc2 Jens Axboe
2018-04-25 17:03 ` Paolo Valente
2018-04-25 17:06   ` Jens Axboe [this message]
2018-04-25 17:25     ` Paolo Valente
2018-04-25 17:34       ` Jens Axboe
2018-04-25 18:02         ` Paolo Valente
2018-04-25 18:18           ` Jens Axboe
2018-04-25 18:42             ` Paolo Valente
2018-04-27  7:57               ` Paolo Valente
2018-04-27 14:29                 ` Jens Axboe
2018-04-27 17:55                   ` 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=96816828-4521-0bab-df73-1e2ecddd7f77@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=paolo.valente@linaro.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