From: Eric Sesterhenn / Snakebyte <snakebyte@gmx.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Eric Sesterhenn / Snakebyte <snakebyte@gmx.de>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Chuck Lever <chucklever@gmail.com>
Subject: Re: [Fwd: Re: [Patch] Possible dereference in fs/nfsd/nfs4callback.c]
Date: Wed, 27 Sep 2006 16:00:44 +0200 [thread overview]
Message-ID: <20060927140044.GA24490@alice> (raw)
In-Reply-To: <1159301581.5492.44.camel@lade.trondhjem.org>
* Trond Myklebust (trond.myklebust@fys.uio.no) wrote:
> On Tue, 2006-09-26 at 15:37 -0400, Chuck Lever wrote:
> > Getting rid of the check makes the code slightly clearer, does not
> > change the characteristic that the code will oops if inode == NULL,
> > and has the side advantage of shutting up coverity checking. That's
> > all my patch does.
>
> That would be fine.
marked 1372, 1373 and 847 as BUG, they will dissappear from
coverity once the patches hit linus tree. Chuck, will you
do the patch for 847 which drops the ENOENT or should i submit one?
1034 is marked as FALSE in coverity, i will submit 1110 and 733
to the bugzilla as soon as i get my password
should I submit further coverity warnings to this list,
if some appear in the future?
Thanks, Eric
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-09-27 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <451962BD.6050909@oracle.com>
2006-09-26 17:36 ` [Fwd: Re: [Patch] Possible dereference in fs/nfsd/nfs4callback.c] Chuck Lever
2006-09-26 18:23 ` J. Bruce Fields
2006-09-26 18:55 ` Trond Myklebust
2006-09-26 19:37 ` Chuck Lever
2006-09-26 20:13 ` Trond Myklebust
2006-09-27 14:00 ` Eric Sesterhenn / Snakebyte [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=20060927140044.GA24490@alice \
--to=snakebyte@gmx.de \
--cc=chucklever@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.