From: Andreas Gruenbacher Subject: Re: Linux 2.6.36-rc7 Date: Fri, 8 Oct 2010 23:50:00 +0200 Message-ID: <201010082350.01135.agruen@suse.de> References: <201010081406.10190.agruen@suse.de> <4CAF47F3.3070800@caviumnetworks.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: Eric Paris , Alan Cox , Tvrtko Ursulin , Linus Torvalds , Linux Kernel Mailing List , Christoph Hellwig , linux-fsdevel@vger.kernel.org To: David Daney Return-path: In-Reply-To: <4CAF47F3.3070800@caviumnetworks.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Friday 08 October 2010 18:33:55 David Daney wrote: > On 10/08/2010 05:06 AM, Andreas Gruenbacher wrote: > > On Thursday 07 October 2010 19:49:28 Eric Paris wrote: > >> The safest thing would probably be to punt the syscalls to 2.6.37. > >> Which is sad since I know a number of people are already working against > >> them, but maybe that proves it's the best approach? > > > > I agree with removing the syscalls from 2.6.36 because of the following > > reasons: > > How would the mechanics of this be achieved? > > Is it enough to just unconditionally return -ENOSYS from the sys_*() > functions? Or should all the patches be reverted? Whatever works I guess ... they would get reactivated pretty soon, anyway. Andreas