From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NXJzO-0006rj-P3 for qemu-devel@nongnu.org; Tue, 19 Jan 2010 14:43:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NXJzJ-0006kd-MF for qemu-devel@nongnu.org; Tue, 19 Jan 2010 14:43:46 -0500 Received: from [199.232.76.173] (port=55072 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NXJzJ-0006kO-Ff for qemu-devel@nongnu.org; Tue, 19 Jan 2010 14:43:41 -0500 Received: from qw-out-1920.google.com ([74.125.92.150]:24735) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NXJzJ-0002Zz-5C for qemu-devel@nongnu.org; Tue, 19 Jan 2010 14:43:41 -0500 Received: by qw-out-1920.google.com with SMTP id 4so9738qwk.4 for ; Tue, 19 Jan 2010 11:43:40 -0800 (PST) Message-ID: <4B560B6A.4090303@codemonkey.ws> Date: Tue, 19 Jan 2010 13:43:38 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 01/14] Introduce qemu_write_full() References: <1262223199-19062-1-git-send-email-kirill@shutemov.name> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Kirill A. Shutemov" Cc: qemu-devel@nongnu.org, Juan Quintela On 01/19/2010 06:17 AM, Kirill A. Shutemov wrote: > On Tue, Jan 19, 2010 at 2:11 PM, Juan Quintela wrote: > >> "Kirill A. Shutemov" wrote: >> >>> A variant of write(2) which handles partial write. >>> >>> Signed-off-by: Kirill A. Shutemov >>> >> Hi >> >> Have you updated this series? Is there any reason that you know when >> they haven't been picked? >> > I don't know any reason, but I'm going to review it once again. > > I also have plan to get rid of -fno-strict-aliasing where it's possible. > I haven't reviewed the series in detail, but generally speaking I don't feel that good about these sort of series. You're essentially adding dummy error handling to quiet the compiler. That's worse than just disabling -Werror because at least you aren't losing the information in the code. If you're going to update error handling, it should be part of an effort to make code paths resilient to error. IOW, actually audit the full error path of the function and make it deal with errors gracefully. Regards, Anthony Liguori > >