Return-Path: <linux-nfs-owner@vger.kernel.org>
Received: from relay4-d.mail.gandi.net ([217.70.183.196]:59540 "EHLO
	relay4-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756590AbcCRGAD (ORCPT
	<rfc822;linux-nfs@vger.kernel.org>); Fri, 18 Mar 2016 02:00:03 -0400
Date: Fri, 18 Mar 2016 09:00:00 +0300
From: Alexey Dvoichenkov <xale@hyperplane.net>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>, spender@grsecurity.net
Subject: Re: nfs_super_set_maxbytes patch
Message-Id: <20160318090000.f72921c7bf0b2d48c2ebdda2@hyperplane.net>
In-Reply-To: <CAHQdGtREL65zXvkdqJ8=hrSXWVyLBGCTAfdO02cXPsC6W26ZVQ@mail.gmail.com>
References: <20160317141307.531709bf667a915973060eae@hyperplane.net>
	<CAHQdGtREL65zXvkdqJ8=hrSXWVyLBGCTAfdO02cXPsC6W26ZVQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-nfs-owner@vger.kernel.org
List-ID: <linux-nfs.vger.kernel.org>

On Thu, 17 Mar 2016 09:20:14 -0400
Trond Myklebust <trond.myklebust@primarydata.com> wrote:

> Why are we having to change _correct_ code in order to work with a
> checking tool?

Oh, and I guess it could be fixed in GRSEC instead.

-- AD