linux-kernel - Re: [V9fs-developer] [PATCH 04/10] 9p: move dirread to fs layer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f158dc670810090640s408626f6mc787cb96efeb155a@mail.gmail.com>
Date:	Thu, 9 Oct 2008 07:40:18 -0600
From:	"Latchesar Ionkov" <lucho@...kov.net>
To:	"Eric Van Hensbergen" <ericvh@...il.com>
Cc:	linux-kernel@...r.kernel.org, v9fs-developer@...ts.sourceforge.net
Subject: Re: [V9fs-developer] [PATCH 04/10] 9p: move dirread to fs layer

I don't think that there is anything at the moment that uses dirread,
but the remote framebuffer that Abishek is working on uses some other
of the client operations.

Thanks,
    Lucho

On Wed, Oct 8, 2008 at 5:12 PM, Eric Van Hensbergen <ericvh@...il.com> wrote:
> On Wed, Oct 8, 2008 at 5:10 PM, Latchesar Ionkov <lucho@...kov.net> wrote:
>> The idea of the client implementation is to be able to use it not only
>> from the vfs layer, but also without it. For example, creating a
>> device that connect to a remote 9P file server.
>>
>
> That does make sense in principal -- although I'm not sure filldir
> structures are the easiest things to work with either.   The main idea
> was to restrict the client.c code to wire operations, primarily
> torwards the idea of treating the "client" as a proxy server once the
> in-kernel-server code goes in (hopefully in 2.6.29).
> Of course the other factor is that this patch-set is gearing up
> towards an alternate extended-POSIX-support approach (what I've been
> referring to as .L) -- that extension will include a wire operation
> which more closely matches linux's concept of dirread (just grab the
> files, not the associated stat) -- but whether or not that is useful
> will largely depend on what sort of remote server you are accessing.
>
> The Plan 9 dirread is one of those special cases where even though its
> not a wire operation, it needs some intimate understanding of the
> underlying protocol (at least  how stats get marshalled) -- in some
> ways if it were a client operation, it might make more sense to pass
> it an array of p9_stat structs to populate with the results.
>
> Do you have some code which used the old client interface I could look
> at or were you just thinking towards the future?
>
>         -eric
>
--
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/