linux-ext4 - Re: RIP [<ffffffff812c3b77>] ext4_release_file+0x37/0xc0 with 4.5-rc6 when resuming from suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160306191010.GM10297@thunk.org>
Date:	Sun, 6 Mar 2016 14:10:10 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Stefan Assmann <sassmann@...nic.de>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: RIP [<ffffffff812c3b77>] ext4_release_file+0x37/0xc0 with
 4.5-rc6 when resuming from suspend

On Sat, Mar 05, 2016 at 11:24:46AM +0100, Stefan Assmann wrote:
> Occasionally when trying to resume from suspend to RAM I get the
> following GPF.
> 
>   Stefan
> 
> [  882.344245] PM: resume of devices complete after 83682.775 msecs
> [  882.420550] PM: Finishing wakeup.
> [  882.420551] Restarting tasks ...·
> [  882.420664] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
> [  882.421141] done.
> [  882.422027] usb 3-9.1.1: USB disconnect, device number 33

Hmm.... did you have a ext4 file system mounted on some kind of USB
attached storage device (USB thumb drive, USB HDD, etc.)?

> [  882.461578] RIP: 0010:[<ffffffff812c3b77>]  [<ffffffff812c3b77>] ext4_release_file+0x37/0xc0

Also, can you translate this address to a file and line number?  Use
the command:

addr2line -e /usr/src/linux/vmlinux -i -a ffffffff812c3b77

Also, if you could give the lines around fs/ext4/file.c (unless it is
exactly 4.5-rc6 without any other changes or commit) that would also
be helpful.

I don't see anything in ext4_release_file() that would obviously be a
potential problem after a suspend/reasume.  One possibly is that some
other piece of code is corrupting memory.

> [  882.459687] CPU: 7 PID: 5299 Comm: dhclient Tainted: G        W       4.5.0-0.rc6.git1.1.vanilla.knurd.1.fc23.x86_64 #1

Is it always dhclient which is trying to exit?

If you can give a detailed description of your hardware configuration
(what devices, what file systems / partitions you have mounted, etc.)
that would be helpful.

Thanks,

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html