[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a4e6962a0808281110s6ee6c86ak3ff6e28c51981656@mail.gmail.com>
Date: Thu, 28 Aug 2008 11:10:21 -0700
From: "Eric Van Hensbergen" <ericvh@...il.com>
To: "Abhishek Kulkarni" <kulkarni@...l.gov>
Cc: v9fs-developer@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] 9p bug fix: return non-zero error value in p9_put_data
On Tue, Aug 26, 2008 at 10:30 AM, Abhishek Kulkarni <kulkarni@...l.gov> wrote:
> p9_put_data is called by p9_create_twrite which expects it to return a
> non-zero value on error. This was the reason why every p9_client_write
> was failing. This patch also adds a check for buffer overflow in
> p9_put_data.
>
I'm a bit confused about when this is even getting called -- O thought
all writes were following the p9_client_uwrite path?
Also, we do the bufoverflow check in p9_create_write -- so with your
patch aren't we doing this twice?
-eric
> Signed-off-by: Abhishek Kulkarni <kulkarni@...l.gov>
> ---
> net/9p/conv.c | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
> diff --git a/net/9p/conv.c b/net/9p/conv.c
> index 4454720..7f6db15 100644
> --- a/net/9p/conv.c
> +++ b/net/9p/conv.c
> @@ -451,8 +451,11 @@ p9_put_data(struct cbuf *bufp, const char *data,
> int count,
> unsigned char **pdata)
> {
> *pdata = buf_alloc(bufp, count);
> + if (buf_check_overflow(bufp))
> + return -EIO;
> +
> memmove(*pdata, data, count);
> - return count;
> + return 0;
> }
>
> static int
>
>
> Thanks,
> -- Abhishek
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists