Linux NFS development
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: linux-nfs@vger.kernel.org
Subject: Re: knfsd: clean up nfsd filesystem interfaces
Date: Tue, 25 Aug 2015 09:03:45 +0300	[thread overview]
Message-ID: <20150825060345.GV5610@mwanda> (raw)
In-Reply-To: <20150822185618.41d20096@tlielax.poochiereds.net>

On Sat, Aug 22, 2015 at 06:56:18PM -0400, Jeff Layton wrote:
> I think we need to keep that check there (or something like it), even if
> just to future-proof this code. But, I am open to suggestions on ways to
> make the static checker happy.
> 

Eventually (and not too far into the future actually) I will fix Smatch
so that it knows that the callers never use size more than
SIMPLE_TRANSACTION_LIMIT so it won't print this error.

So I guess we can keep the check.

regards,
dan carpenter


      reply	other threads:[~2015-08-25  6:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-22 19:58 knfsd: clean up nfsd filesystem interfaces Dan Carpenter
2015-08-22 22:56 ` Jeff Layton
2015-08-25  6:03   ` Dan Carpenter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150825060345.GV5610@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=jlayton@poochiereds.net \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox