From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
lkft-triage@lists.linaro.org, stable@vger.kernel.org,
linux-ext4@vger.kernel.org,
Arthur Marsh <arthur.marsh@internode.on.net>,
Richard Weinberger <richard.weinberger@gmail.com>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH 4.19 000/105] 4.19.45-stable review
Date: Tue, 21 May 2019 10:59:56 +0200 [thread overview]
Message-ID: <20190521085956.GC31445@kroah.com> (raw)
In-Reply-To: <20190520222342.wtsjx227c6qbkuua@xps.therub.org>
On Mon, May 20, 2019 at 05:23:42PM -0500, Dan Rue wrote:
> On Mon, May 20, 2019 at 02:13:06PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.19.45 release.
> > There are 105 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed 22 May 2019 11:50:49 AM UTC.
> > Anything received after that time might be too late.
>
> We're seeing an ext4 issue previously reported at
> https://lore.kernel.org/lkml/20190514092054.GA6949@osiris.
>
> [ 1916.032087] EXT4-fs error (device sda): ext4_find_extent:909: inode #8: comm jbd2/sda-8: pblk 121667583 bad header/extent: invalid extent entries - magic f30a, entries 8, max 340(340), depth 0(0)
> [ 1916.073840] jbd2_journal_bmap: journal block not found at offset 4455 on sda-8
> [ 1916.081071] Aborting journal on device sda-8.
> [ 1916.348652] EXT4-fs error (device sda): ext4_journal_check_start:61: Detected aborted journal
> [ 1916.357222] EXT4-fs (sda): Remounting filesystem read-only
>
> This is seen on 4.19-rc, 5.0-rc, mainline, and next. We don't have data
> for 5.1-rc yet, which is presumably also affected in this RC round.
>
> We only see this on x86_64 and i386 devices - though our hardware setups
> vary so it could be coincidence.
>
> I have to run out now, but I'll come back and work on a reproducer and
> bisection later tonight and tomorrow.
>
> Here is an example test run; link goes to the spot in the ltp syscalls
> test where the disk goes into read-only mode.
> https://lkft.validation.linaro.org/scheduler/job/735468#L8081
Odd, I keep hearing rumors of ext4 issues right now, but nothing
actually solid that I can point to. Any help you can provide here would
be great.
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-21 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190520115247.060821231@linuxfoundation.org>
2019-05-20 22:23 ` [PATCH 4.19 000/105] 4.19.45-stable review Dan Rue
2019-05-21 8:59 ` Greg Kroah-Hartman [this message]
2019-05-21 9:28 ` Naresh Kamboju
2019-05-21 9:38 ` ext4 regression (was Re: [PATCH 4.19 000/105] 4.19.45-stable review) Greg Kroah-Hartman
2019-05-21 10:28 ` Naresh Kamboju
2019-05-21 16:21 ` Theodore Ts'o
2019-05-21 16:30 ` Greg Kroah-Hartman
2019-05-21 16:44 ` Greg Kroah-Hartman
2019-05-21 17:57 ` Naresh Kamboju
2019-05-22 5:05 ` Theodore Ts'o
2019-05-22 10:20 ` Naresh Kamboju
2019-05-21 15:02 ` Dan Rue
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=20190521085956.GC31445@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arthur.marsh@internode.on.net \
--cc=ben.hutchings@codethink.co.uk \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=richard.weinberger@gmail.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).