Message-ID: <55706265.8020609@message-id.googlemail.com>
Date: Thu, 04 Jun 2015 16:36:21 +0200
From: Stefan Seyfried <stefan.seyfried@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Ming Lei <tom.leiming@gmail.com>
CC: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] 4.1-rc6 unloading loop OOPS
References: <55701655.9000605@message-id.googlemail.com> <CACVXFVMor88EM7=qpHZtg8MST8-b=oBUiW9aNE4CX2w3UcamuQ@mail.gmail.com>
In-Reply-To: <CACVXFVMor88EM7=qpHZtg8MST8-b=oBUiW9aNE4CX2w3UcamuQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1247
Lines: 38

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@googlemail.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/