From: David Miller <davem@davemloft.net>
To: roel.kluin@gmail.com
Cc: ericvh@gmail.com, rminnich@sandia.gov, lucho@ionkov.net,
v9fs-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/9p: fid->fid is used uninitialized
Date: Sun, 18 Jan 2009 21:33:08 -0800 (PST) [thread overview]
Message-ID: <20090118.213308.214103172.davem@davemloft.net> (raw)
In-Reply-To: <49737EA1.3080805@gmail.com>
From: Roel Kluin <roel.kluin@gmail.com>
Date: Sun, 18 Jan 2009 20:10:25 +0100
> fid->fid is used uninitialized
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
Applied, thanks Roel.
Someone should look into how p9_idpool_get() errors are
propagated. Another call site uses -ENOBUFS, this location
uses -ENOSPC, and it begs the question whether we should
just use the error return given by p9_idpool_get() across
the board.
prev parent reply other threads:[~2009-01-19 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 19:10 Roel Kluin
2009-01-19 5:33 ` David Miller [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=20090118.213308.214103172.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=rminnich@sandia.gov \
--cc=roel.kluin@gmail.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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
Powered by JetHome