Trond Myklebust [EMAIL PROTECTED] wrote:
We've come across an interesting problem with NFS4 mount on a PPC64 box. If
the mount program is compiled as PPC32, then the mount() syscall is returned
EFAULT.
So, why is this not a case of Doctor it hurts...?
Because:
(1) The kernel is
Christoph Hellwig [EMAIL PROTECTED] wrote:
I don't think we should encourage filesystem writers to do such stupid
things as ncfps/smbfs do. In fact I'm totally unhappy thay nfs4 went
down that road.
The problem with NFS4, I think, is that the mount syscall sets a hard limit on
the amount of
Trond Myklebust [EMAIL PROTECTED] wrote:
Without such a library, it is pointless to contemplate other callers.
With such a library, you will have a single point for switching between
32bit and 64 bit.
Other callers include such as busybox, sash and uClinux. I'm not sure about
such as Perl,
m den 18.04.2005 Klokka 16:23 (+0100) skreiv David Howells:
Trond Myklebust [EMAIL PROTECTED] wrote:
Without such a library, it is pointless to contemplate other callers.
With such a library, you will have a single point for switching between
32bit and 64 bit.
Other callers include
On Fri, Apr 15, 2005 at 01:22:59PM -0700, David S. Miller wrote:
Make a -compat_read_super() just like we have a -compat_ioctl()
method for files, if you want to suggest a solution like what
you describe.
I don't think we should encourage filesystem writers to do such stupid
things as
On Mon, Apr 18, 2005 at 10:07:14AM -0700, Bryan Henderson wrote:
On Fri, Apr 15, 2005 at 01:22:59PM -0700, David S. Miller wrote:
Make a -compat_read_super() just like we have a -compat_ioctl()
method for files, if you want to suggest a solution like what
you describe.
I don't think
mount() is not a documented syscall. The binary formats for filesystems
like NFS are only documented inside the kernels to which they apply.
What _is_ a documented system call? Linux is famous for not having
documented interfaces (or, put another way, not distinguishing between an
interface
- unit of disk space allocation for the kernel image file is
block. That is, optimizations like UFS fragments or reiserfs tails are
not applied, and
- blocks that kernel image is stored into are real disk blocks (i.e.,
there is a way to disable delayed allocation), and
- kernel image file
Al Viro [EMAIL PROTECTED] wrote:
Architecture-dependent blob passed to mount(2) (aka nfs4_mount_data).
If you want it to be a blob, at least have a decency to use encoding
that would not depend on alignment rules and word size. Hell, you
could use XDR - it's not that nfs would need
On Mon, Apr 18, 2005 at 06:33:09PM +0100, David Howells wrote:
Al Viro [EMAIL PROTECTED] wrote:
Architecture-dependent blob passed to mount(2) (aka nfs4_mount_data).
If you want it to be a blob, at least have a decency to use encoding
that would not depend on alignment rules and word
m den 18.04.2005 Klokka 10:17 (-0700) skreiv Bryan Henderson:
mount() is not a documented syscall. The binary formats for filesystems
like NFS are only documented inside the kernels to which they apply.
What _is_ a documented system call? Linux is famous for not having
documented
On Mon, 18 Apr 2005 11:36:25 +0100
David Howells [EMAIL PROTECTED] wrote:
Christoph Hellwig [EMAIL PROTECTED] wrote:
I don't think we should encourage filesystem writers to do such stupid
things as ncfps/smbfs do. In fact I'm totally unhappy thay nfs4 went
down that road.
The problem
Hello,
The audit subsystem is currently incapable of auditing a file system object
based on its location and name. This is critical for auditing well-defined
and security-relevant locations such as /etc/shadow, where the file is
re-created on each transaction, and cannot rely on the (device,
m den 18.04.2005 Klokka 15:07 (-0700) skreiv Bryan Henderson:
We're already up to version 6 of the binary interfaces for v2/v3, and if
you count NFSv4 too, then that makes 7.
I don't know the NFS mount option format, but I'm having a hard time
imagining how a string-based format can take
Martin Jambor wrote:
Hi all,
I am a member of a group that implements a filesystem that allocates
disk blocks to in-memory blocks lazily, that means, the decision is
made just before the data are actually sent to disk. Moreover, when
cached pages are modified, the data can be (and almost certainly
15 matches
Mail list logo
