linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Meelis Roos <mroos@linux.ee>
Cc: <linux-alpha@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	<linux-block@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28
Date: Sat, 16 Feb 2019 12:45:36 -0500	[thread overview]
Message-ID: <20190216174536.GC23000@mit.edu> (raw)
In-Reply-To: <076b8b72-fab0-ea98-f32f-f48949585f9d@linux.ee>

On Fri, Feb 15, 2019 at 06:59:48PM +0200, Meelis Roos wrote:
> The result of the bisection is
> [88dbcbb3a4847f5e6dfeae952d3105497700c128] blkdev: avoid migration stalls for blkdev pages
> 
> Is that result relevant for the problem or should I continue bisecting between 4.20.0 and the so far first bad commit?

Can you try reverting the commit and see if it makes the problem go away?

    	    	      	  	     - Ted

  reply	other threads:[~2019-02-16 17:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 15:52 ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28 Meelis Roos
2019-02-10 20:27 ` Meelis Roos
2019-02-15 16:59   ` Meelis Roos
2019-02-16 17:45     ` Theodore Y. Ts'o [this message]
2019-02-16 22:29       ` Meelis Roos
2019-02-18 12:02         ` Jan Kara
2019-02-18 12:37           ` Meelis Roos
2019-02-19 12:17           ` Meelis Roos
2019-02-19 13:20             ` Jan Kara
2019-02-19 13:49               ` Meelis Roos
2019-02-19 14:44               ` Matthew Wilcox
2019-02-20  6:31                 ` Meelis Roos
2019-02-20  9:48                   ` Jan Kara
2019-02-20 23:23                     ` Meelis Roos
2019-02-21 13:29                       ` Jan Kara
2022-08-25 15:05                         ` matoro
2022-08-26 10:55                           ` Jan Kara
2022-08-26 11:04                             ` Vlastimil Babka
2022-08-26 16:16                               ` matoro

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=20190216174536.GC23000@mit.edu \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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).