From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Holler Date: Mon, 04 Feb 2013 12:05:29 +0000 Subject: Re: [PATCH 2/3 v2] fb: udlfb: fix hang at disconnect Message-Id: <510FA409.2080201@ahsoftware.de> List-Id: References: <50F2A310.5010006@ahsoftware.de> <1359139768-32294-1-git-send-email-holler@ahsoftware.de> <1359139768-32294-2-git-send-email-holler@ahsoftware.de> <20130128162238.7fba92fe.akpm@linux-foundation.org> <51071E21.9030008@ahsoftware.de> <5107A5ED.7020009@ahsoftware.de> <5107AE4F.9000809@ahsoftware.de> <5107F014.4030704@ahsoftware.de> <5108329E.2050802@ahsoftware.de> <20130204011413.GA6413@kroah.com> In-Reply-To: <20130204011413.GA6413@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Greg KH Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org, Florian Tobias Schandinat , Bernie Thompson , Steve Glendinning , stable@vger.kernel.org Am 04.02.2013 02:14, schrieb Greg KH: > So you are right in that your driver will wait for forever for a > disconnect() to happen, as it will never be called. I don't understand > the problem that this is causing when it happens. What's wrong with > udlfb that having the cpu suddently reset as the powerdown happened > without it knowing about it? There is nothing wrong with that. I've just explained why a problem doesn't occur on shutdown but on disconnect (of the device). Regards, Alexander