From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Myers Subject: Re: [PATCH] xfs: prevent stack overflows from page cache allocation Date: Thu, 24 Oct 2013 11:41:15 -0500 Message-ID: <20131024164115.GU1935@sgi.com> References: <1382585110-1796-1-git-send-email-david@fromorbit.com> <20131024084803.GA28144@infradead.org> <20131024103751.GS2797@dastard> <20131024154220.GA19055@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com To: Christoph Hellwig Return-path: Content-Disposition: inline In-Reply-To: <20131024154220.GA19055@infradead.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org Hey, On Thu, Oct 24, 2013 at 08:42:20AM -0700, Christoph Hellwig wrote: > On Thu, Oct 24, 2013 at 09:37:51PM +1100, Dave Chinner wrote: > > Sure, if you want to. But doing that shouldn't prevent this fix from > > being committed in the mean time, especially as other filesystems > > already use this method for avoiding these problems. > > I'd much prefer aiming for the proper fix first. If for some reason we > can't get it done in time the workaround can be applied. Dave probably has a customer waiting on this. If pulling this in will make a proper fix more difficult to do I can understand keeping the patch out. Otherwise, can't we just remove this along with the other filesystems' equivalent code when the proper fix is committed? Regards, Ben _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs