Matthew Dillon wrote:
> The only major bugfixes that have not been backported from -current to
> -stable in regards to NFS are the NFS/TCP fix, which is being backported
> now, and a number of fixes to the VM system when dealing with mmap(),
> which cannot be backported until we backport the entire -current VM
> system.
Ok, that's good news. I'd like to stick with -stable if I can. No
pressure, but do you have an ETA on the VM backport? I'm assuming that
something like that is "down the road," probably after 3.2?
> The mmap() breakage is unavoidable in -stable but hopefully will not cause
> serious problems for people. The breakage is related to garbarge showing
> up in the mmap()'d pages *after* the logical file EOF. That is, if you
> have a 500 byte file and mmap() it into a 4K page, data occuring after
> offset 500 may or may not be 0.
Hrrrmm... ok. So what could happen due to this bug, and how would I
spot it? Meanwhile I'll keep an eye on the commits for that NFS
backport. Thanks muchly for the update. :)
Doug
--
*** Chief Operations Officer, DALnet IRC network ***
Nominated for quote of the year is the statement made by Representative
Dick Armey (Texas), who when asked if he were in the President's place,
would he resign, responded:
"If I were in the President's place I would not get a chance to resign.
I would be lying in a pool of my own blood hearing Mrs. Armey standing
over me saying, 'How do I reload this damn thing?'"
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
