Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2

From: Manfred Spraul (manfreds@colorfullife.com)
Date: Tue Apr 04 2000 - 10:00:19 EST

Next message: Tim Waugh: "Re: whats about the bootup code ?"
Previous message: Jim Breton: "mad dmesg output with via-rhine driver"
In reply to: Jamie Lokier: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
Next in thread: Jeff V. Merkey: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
Reply: Jeff V. Merkey: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: "Jamie Lokier" <lk@tantalophile.demon.co.uk>
>
> Which is unfortunate because the computed LSEEK_CUR appears in Glibc's
> readdir(). It's a corner case. To remove the LSEEK_CUR, unfortunately
> you have to use another syscall in the normal case.
>
I don't see a problem with LSEEK_CUR, as long as glibc doesn't make any
assumptions about the number.

If they just substract one offset from another, the there should be no
problem:
default_llseek(LSEEK_CUR) adds the current position.

Do they assume that the offset is always ascending, or any other foolish
ideas?

-- Manfred

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

Next message: Tim Waugh: "Re: whats about the bootup code ?"
Previous message: Jim Breton: "mad dmesg output with via-rhine driver"
In reply to: Jamie Lokier: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
Next in thread: Jeff V. Merkey: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
Reply: Jeff V. Merkey: "Re: DCACHE Pinning Problems with rm -r on 2.2.15/2.3.99Pre3 withNWFS2.2.2"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:12 EST