From: Benny Halevy <bhalevy@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/2] fix getdevice{info,list} xdr decode sizing
Date: Thu, 02 Sep 2010 10:57:45 +0300 [thread overview]
Message-ID: <4C7F58F9.4080306@panasas.com> (raw)
looks like encode_getdevice{info,list} went under the radar and they
do not update hdr->replen.
decode_getdeviceinfo_maxsz was completely screwed up so that twas fixed
along with the replen calculation for the deviceinfo's xdr_inline_pages.
next reply other threads:[~2010-09-02 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 7:57 Benny Halevy [this message]
2010-09-02 7:58 ` [PATCH 1/2] SQUASHME: pnfs-submit: fix getdeviceinfo decode sizing Benny Halevy
2010-09-02 7:59 ` [PATCH 2/2] SQUASHME: pnfs-submit: fix getdevicelist " Benny Halevy
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=4C7F58F9.4080306@panasas.com \
--to=bhalevy@panasas.com \
--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 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.