From: "David S. Miller" <davem@redhat.com>
To: "Petri T. Koistinen" <petri.koistinen@iki.fi>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/sunrpc/svcauth_unix.c: unix_domain_find: return NULL if kmalloc fails
Date: Mon, 26 Apr 2004 16:37:58 -0700 [thread overview]
Message-ID: <20040426163758.4a407cb4.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0404261913550.5531@dsl-prvgw1cc4.dial.inet.fi>
On Mon, 26 Apr 2004 19:17:19 +0300 (EEST)
"Petri T. Koistinen" <petri.koistinen@iki.fi> wrote:
> I browsed http://linuxbugs.coverity.com/ site and found this:
>
> NULL_RETURNS error: Dereference of possibly NULL ptr "new" returned by "kmalloc".
...
> Is this correct fix? What happens when unix_domain_find return NULL?
next prev parent reply other threads:[~2004-04-26 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 16:17 [PATCH] net/sunrpc/svcauth_unix.c: unix_domain_find: return NULL if kmalloc fails Petri T. Koistinen
2004-04-26 16:45 ` J. Bruce Fields
2004-04-26 23:37 ` David S. Miller [this message]
2004-04-26 23:38 ` David S. Miller
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=20040426163758.4a407cb4.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=petri.koistinen@iki.fi \
/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