From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH 0/2] sys_write() should write all valid data Date: Fri, 15 May 2009 08:52:29 +0200 Message-ID: <87octuq2mq.fsf@basil.nowhere.org> References: <1242317939-15392-1-git-send-email-v.mayatskih@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Josef Bacik , sandeen@redhat.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Vitaly Mayatskikh Return-path: Received: from one.firstfloor.org ([213.235.205.2]:47027 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752793AbZEOGwd (ORCPT ); Fri, 15 May 2009 02:52:33 -0400 In-Reply-To: <1242317939-15392-1-git-send-email-v.mayatskih@gmail.com> (Vitaly Mayatskikh's message of "Thu, 14 May 2009 18:18:59 +0200") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Vitaly Mayatskikh writes: > There's user-visible misbehavour in sys_write(): when user tries to > put down to disk some data, which crosses boundary of existing > memory, sys_write() either immediately returns with EFAULT or writes > first page(s). What's wrong with that? Seems like perfectly fine behaviour to me. Did it break some program of yours? If yes can you describe the scenario? -Andi -- ak@linux.intel.com -- Speaking for myself only.