linux-kernel - Re: [REGRESSION] 4.1-rc6 unloading loop OOPS

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: <55706265.8020609@message-id.googlemail.com>
Date:	Thu, 04 Jun 2015 16:36:21 +0200
From:	Stefan Seyfried <stefan.seyfried@...glemail.com>
To:	Ming Lei <tom.leiming@...il.com>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION] 4.1-rc6 unloading loop OOPS

Hi Ming,

Am 04.06.2015 um 12:24 schrieb Ming Lei:
> On Thu, Jun 4, 2015 at 5:11 PM, Stefan Seyfried
> <stefan.seyfried@...glemail.com> wrote:

>> I can reproduce the backtrace after a reboot once (subsequent modprobe/rmmod loop
>> do not complain anymore), but not the OOPS.
> 
> One fix[1] was just merged to linus tree, and could you test that to see if your
> issue can be addressed?
> 
> [1] http://marc.info/?t=143201518300001&r=1&w=2

I just tried current Linus' master v4.1-rc6-49-g8a7deb3 which contains
this commit and do no longer get the Warning

Unfortunately, due to this I cannot really test your patch for the OOPS
(but the OOPS was only happening once for me, so it was not reliably
triggered).

Thanks, things work well for me, again :-)

Best regards,

	Stefan
-- 
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/