From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Bastien Nocera To: BlueZ development In-Reply-To: <1191513767.10698.148.camel@violet> References: <1191511655.3479.13.camel@cookie.hadess.net> <1191513767.10698.148.camel@violet> Date: Thu, 04 Oct 2007 17:09:57 +0100 Message-Id: <1191514197.3479.16.camel@cookie.hadess.net> Mime-Version: 1.0 Subject: Re: [Bluez-devel] Possible infinite loop in inotify code Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net On Thu, 2007-10-04 at 18:02 +0200, Marcel Holtmann wrote: > Hi Bastien, > > > Uli mentioned a possible infinite loop in some circumstances: > > https://bugzilla.redhat.com/show_bug.cgi?id=235307 > > > > Although I wasn't able to reproduce the bug, the attached patch looks > > technically correct. > > I reworked the patch a little bit and applied it. The G_IO_STATUS_AGAIN > and G_IO_ERROR_AGAIN are not guaranteed to be the same. My mistake, I made the first patch using g_io_channel_read_chars instead of the deprecated g_io_channel_read and changed the code accordingly (including possible retvals), but then remembered eglib. I guess I didn't completely revert those changes. Cheers -- Bastien Nocera ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel