From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Anton V. Boyarshinov" Subject: Re: [PATCH] xf86drm.c: add counter for ioctl restarting Date: Mon, 16 Apr 2012 19:05:48 +0400 Message-ID: <20120416190548.78b1c43c@boyarsh.office.altlinux.ru> References: <20120413172642.4c423352@boyarsh.office.altlinux.ru> <20120413134216.GG4525@phenom.ffwll.local> <20120416125435.6a94f9f9@boyarsh.office.altlinux.ru> <1334585559.17648.4.camel@atropine> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from vint.altlinux.org (vint.altlinux.org [194.107.17.35]) by gabe.freedesktop.org (Postfix) with ESMTP id EACFE9F383 for ; Mon, 16 Apr 2012 08:05:49 -0700 (PDT) In-Reply-To: <1334585559.17648.4.camel@atropine> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Adam Jackson Cc: DRI mailing list List-Id: dri-devel@lists.freedesktop.org Hi > > around this bugs with proper logging (absent in this patch) much better > > than lockup. > > But your workaround isn't harmless. It adds new failure modes for other > cases that currently work. That's worse, not better. I think that from user scope nothing (including Xorg crash) is worth then lock with 2 abilities: reset or network login and kill -9 Xorg. I think that even if ioctl's should be restarted forever as present, some error detecting and logging code should be in this place. Regards, Anton