[bug #28859] remove(3) fails to remove an empty directory

Update of bug #28859 (project hurd): Status:None => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #5: Fixed upstream in cb6

Re: What happens to mappings when closing file?

olafbuddenha...@gmx.net wrote: > Hi, > > I'm trying to understand why filesystem servers need proxy memory > objects for io_map(). Unfortunately, I don't have time to read all the > relevant code right now... After a quick glance, my guess is that the > proxy objects are used so the same pager can

Re: What happens to mappings when closing file?

olafbuddenha...@gmx.net, le Sat 03 Apr 2010 17:38:01 +0200, a écrit : > the proxy objects are used so the same pager can be provided to > several clients mapping the same file, but with different permissions? Yes. > But if several clients share a pager, doesn't that mean there is no way > to shut

[Bug libc/11276] remove(3) fails when unlink(2) returns `EPERM'

--- Additional Comments From drepper at redhat dot com 2010-04-04 09:09 --- Changed in git. -- What|Removed |Added Status|NEW |RESOLVED

What happens to mappings when closing file?

Hi, I'm trying to understand why filesystem servers need proxy memory objects for io_map(). Unfortunately, I don't have time to read all the relevant code right now... After a quick glance, my guess is that the proxy objects are used so the same pager can be provided to several clients mapping the