- User Since
- Mar 12 2014, 1:00 AM (262 w, 1 d)
- Add compiler version guards.
Tue, Mar 19
Ed pointed out that we may not want absolute paths in general. That's probably true, but I'll note that this change just makes things consistent for now. I think mapping the symlink paths is a no-brainer, at least.
Mon, Mar 18
I'm writing a few test cases for mlock as part of the user wiring work. I added one which does the following:
This is broken in a couple of ways:
- bn += blockcnt isn't right if bn is has a partial offset into the indirect block.
- The innermost loop contains a severe bug: it doesn't update ap->in_lbn for the remaining indirect block descriptors, so we may load an indirect block at the wrong logical offset in the vnode. This can cause data corruption if the vnode is subsequently modified.
Sun, Mar 17
This was committed in r345244.
- Update based on Kirk's comment.
Fri, Mar 15
- Describe nbp, runb and runp parameters per kib's suggestion.
- Return ENXIO if the offset is negative. Upper layers do not check this for us.
- Don't use ufs_getlbns() to map direct blocks.
- Assert num == 0 when we break from the loop.
- Readd a comment explaining the return value.
- Rename ufs_readmeta() to ufs_readindir().
Thu, Mar 14
- Don't define bswap*() in <endian.h>.
Wed, Mar 13
Mon, Mar 11
So, I don't yet have a good solution for the mesa build. Hiding the bswap* declarations behind an #if __BSD_VISIBLE guard didn't fix the problem there.
Introduce a wrapper and define __BYTE_ORDER etc.
Sat, Mar 9
Fri, Mar 8
Thu, Mar 7
Wed, Mar 6
Tue, Mar 5
Mon, Mar 4
- Change man page wording.
- Call the flag KVME_FLAG_USER_WIRED; we do not set it if the mapping is wired by vslock().