Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1231808 > unrolled thread

Re: [PATCH 1/3] BTRFS: support NFSv2 export

Started byNeil Brown <neilb@suse.de>
First post2015-09-24 04:10 +0200
Last post2015-10-05 16:40 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 1/3] BTRFS: support NFSv2 export Neil Brown <neilb@suse.de> - 2015-09-24 04:10 +0200
    Re: [PATCH 1/3] BTRFS: support NFSv2 export Chris Mason <clm@fb.com> - 2015-10-05 16:40 +0200

#1231808 — Re: [PATCH 1/3] BTRFS: support NFSv2 export

FromNeil Brown <neilb@suse.de>
Date2015-09-24 04:10 +0200
SubjectRe: [PATCH 1/3] BTRFS: support NFSv2 export
Message-ID<qc48V-5Uv-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

David Sterba <dsterba@suse.cz> writes:

> On Fri, May 08, 2015 at 10:16:23AM +1000, NeilBrown wrote:
>> The "fh_len" passed to ->fh_to_* is not guaranteed to be that same as
>> that returned by encode_fh - it may be larger.
>> 
>> With NFSv2, the filehandle is fixed length, so it may appear longer
>> than expected and be zero-padded.
>> 
>> So we must test that fh_len is at least some value, not exactly equal
>> to it.
>> 
>> Signed-off-by: NeilBrown <neilb@suse.de>
>
> Acked-by: David Sterba <dsterba@suse.cz>

Thanks.  However I just checked mainline and this still hasn't been
applied.
Should I resend it to someone?  Who?

Thanks,
NeilBrown

[toc] | [next] | [standalone]


#1239613

FromChris Mason <clm@fb.com>
Date2015-10-05 16:40 +0200
Message-ID<qgf5M-1ED-21@gated-at.bofh.it>
In reply to#1231808
On Thu, Sep 24, 2015 at 11:59:02AM +1000, Neil Brown wrote:
> David Sterba <dsterba@suse.cz> writes:
> 
> > On Fri, May 08, 2015 at 10:16:23AM +1000, NeilBrown wrote:
> >> The "fh_len" passed to ->fh_to_* is not guaranteed to be that same as
> >> that returned by encode_fh - it may be larger.
> >> 
> >> With NFSv2, the filehandle is fixed length, so it may appear longer
> >> than expected and be zero-padded.
> >> 
> >> So we must test that fh_len is at least some value, not exactly equal
> >> to it.
> >> 
> >> Signed-off-by: NeilBrown <neilb@suse.de>
> >
> > Acked-by: David Sterba <dsterba@suse.cz>
> 
> Thanks.  However I just checked mainline and this still hasn't been
> applied.
> Should I resend it to someone?  Who?


Sorry Neil, I thought you were pushing these after it was ack'd.  I'll
put it in my pull this week.

-chris

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web