From: Pavel Machek <pavel@ucw.cz>
To: Ritesh Harjani <riteshh@linux.ibm.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
peterz@infradead.org, mingo@redhat.com, will@kernel.org,
jack@suse.com, tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org
Subject: Re: 5.8-rc1: new warnings in ext4_mb_new_blocks?
Date: Mon, 15 Jun 2020 17:43:27 +0200 [thread overview]
Message-ID: <20200615154327.GA12506@duo.ucw.cz> (raw)
In-Reply-To: <20200615112749.104AF52054@d06av21.portsmouth.uk.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On Mon 2020-06-15 16:57:48, Ritesh Harjani wrote:
>
>
> On 6/15/20 1:07 PM, Pavel Machek wrote:
> > Hi!
> >
> > Booting 5.8-rc1 on x220, I get scary warnings:
> >
> > [ 7.089941] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: errors=remount-ro
> > [ 7.343231] BUG: using smp_processor_id() in preemptible [00000000] code: systemd-tmpfile/2788
> > [ 7.344052] caller is debug_smp_processor_id+0x17/0x20
> > [ 7.344897] CPU: 3 PID: 2788 Comm: systemd-tmpfile Not tainted 5.8.0-rc1+ #116
> > [ 7.345745] Hardware name: LENOVO 42872WU/42872WU, BIOS 8DET74WW (1.44 ) 03/13/2018
> > [ 7.346561] Call Trace:
> > [ 7.347355] dump_stack+0x60/0x7a
> > [ 7.348170] check_preemption_disabled+0xb1/0xc0
> > [ 7.348951] debug_smp_processor_id+0x17/0x20
> > [ 7.349728] ext4_mb_new_blocks+0x1f2/0x13e0
> >
> > and they continue after boot.
> >
>
> Below should fix this. I guess it couldn't make it to rc1.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?h=ext4-for-linus-5.8-rc1-2&id=811985365378df01386c3cfb7ff716e74ca376d5
>
Thanks for the pointer. That seems to do the job.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2020-06-15 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 7:37 5.8-rc1: new warnings in ext4_mb_new_blocks? Pavel Machek
2020-06-15 11:27 ` Ritesh Harjani
2020-06-15 15:43 ` Pavel Machek [this message]
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=20200615154327.GA12506@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riteshh@linux.ibm.com \
--cc=tytso@mit.edu \
--cc=will@kernel.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