| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it possible to support ftruncate() on non-vnode file types in
the future.
- 'struct fileops' grows a 'fo_truncate' method to handle an ftruncate() on
a given file descriptor.
- ftruncate() moves to kern/sys_generic.c and now just fetches a file
object and invokes fo_truncate().
- The vnode-specific portions of ftruncate() move to vn_truncate() in
vfs_vnops.c which implements fo_truncate() for vnode file types.
- Non-vnode file types return EINVAL in their fo_truncate() method.
Submitted by: rwatson
|
|
|
|
|
|
|
| |
requests.
MFC after: 3 days
Reported by: Michiel Boland michiel boland.org
|
|
|
|
|
|
|
|
|
| |
add correct locking to the operation of unmounting.
This will prevent debugging kernels from panicking if mounting a
non-hpfs partition (I'm not sure if this can be a problem with a
successful mounting operation though).
MFC: 3 days
|
| |
|
|
|
|
| |
- ipmi(4) appeared in FreeBSD 6.2, not in 6.3
|
|
|
|
|
|
| |
Submitted by: brix,
Michael Fuckner <michael@fuckner.net>
MFC after: 0 days
|
|
|
|
| |
Approved by: thompsa (mentor)
|
| |
|
|
|
|
|
|
| |
PR: kern/119351
Submitted by: Takeharu KATO <takeharu1219@ybb.ne.jp>
MFC after: 1 week
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
|
|
|
|
|
|
|
| |
CVSROOT/config file options that control keyword expansion. cvs-1.12 has
its own $Id$ expansion controls and they're configured in CVSROOT/config
rather than CVSROOT/options. The problem is that current cvs-1.11.x
doesn't understand the future keywords.....
Add trivial forward support for the new keywords for when cvs-1.12
hits the tree down the road. CVSROOT/options won't be going away - cvsup
uses it.
|
| |
|
|
|
|
| |
this was missed in the initial import
|
| |
|
|
|
|
|
|
| |
pv_list_count from struct md_page. Ever since Peter rewrote the pv
entry allocator for amd64 and i386 pv_list_count has been correctly
maintained but otherwise unused.
|
|
|
|
|
| |
This is unfortunately necessary with some flash based devices which can
get hundreds of seconds behind with softupdates enabled.
|
| |
|
| |
|
|
|
|
| |
utilized .Tn and capitalized PCI).
|
| |
|
|
|
|
|
|
|
|
| |
instead of original user-mode string in the linux_stat() and
linux_lstat() syscalls.
Tested by: Peter Holm
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
- spell 16384 as 16384 and not as BKVASIZE. 16384 is (not quite) just a
magic size that works well in practice. BKVASIZE should be MAXBSIZE
(65536), but is 16384 because i386's don't have enough kva for it to
be MAXBSIZE; 16384 works (not so well) for it for much the same reasons
that it works well in the heuristic.
- expand and/or add comments about this and other details.
- don't explicitly inline this function.
- fix some other style bugs.
|
|
|
|
|
|
| |
ABI override binary isn't found. This could probably be smoother, but
it is what I did in p4 change #126891 on 2007/09/27. It should solve
the "ld-elf32.so.1"-in-chroot problem.
|
|
|
|
| |
Reported by: Peter Jeremy <peterjeremy@optushome.com.au>
|
|
|
|
| |
MFC after: 0 days
|
|
|
|
| |
MFC after: 0 days
|
|
|
|
| |
gets the ball rolling.
|
|
|
|
| |
today, rather than details relevant only to the 3.x pci driver.
|
|
|
|
|
|
| |
Reported and tested by: Peter Holm
Reviewed by: alc
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
default. This has the disadvantage of rendering the datasize resource
limit irrelevant, but without this change, legitimate uses of more
memory than will fit in the data segment are thwarted by default.
Fix chunk_alloc_mmap() to work correctly if initial mapping is not
chunk-aligned and mapping extension fails.
|
|
|
|
|
|
| |
Reported by: Yoshihiko Sarumaru <mistral at imasy.or.jp>
Reviewed by: trhodes
MFC-after: 3 days
|
|
|
|
|
|
| |
of home-rolled [iu][248] in the ZIP support code.
Approved by: kientzle
|
|
|
|
|
|
|
|
| |
the number of bytes read is actually not important as long as we have at
least what we ask for. Illustrate its benefits by using it throughout
the ZIP support code, except for the few cases where it doesn't apply.
Approved by: kientzle
|
|
|
|
|
|
| |
While here change %d to %u for u_ints.
Discussed with: rwatson, kmacy
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
allocation, free the indirect blocks before clearing the disk pointers,
that could lead to the softupdate inconsistencies in the case of the
machine or disk crash at the wrong time.
Rearrange the recover code to do the ffs_blkfree() after the second
ffs_syncvnode(), that clears the pointers chain.
Proposed and reviewed by: tegge
Tested by: Peter Holm
MFC after: 3 weeks
|
|
|
|
|
|
|
| |
superpage promotion.
Correct a style error in kmem_malloc(): pmap_enter()'s last parameter is
a Boolean.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
happen if there are no files open. Accounting for these can
eventually return a negative value for olenp causing sysctl to
crash with a bad malloc.
Reported by: Pawel Worach <pawel.worach@gmail.com>
|
|
|
|
| |
change fixes output for break() on LP64 systems.
|
|
|
|
|
|
|
| |
+ kread is not a boolean, so check it as such
+ fix $FreeBSD$ Ids
+ denote copyrights with /*-
+ misc whitespace changes.
|
|
|
|
|
|
|
|
|
|
|
|
| |
set, announce BIO_DELETE capability and issue ATA_CFA_ERASE when we get one.
Once we issue more BIO_DELETE, this will improve lifetime, and
possibly write speed of Flash based devices which have usable flash
adaptation layers.
For now, about the only usage is the newfs(1) -E flag.
Approved by: sos
|
|
|
|
|
|
|
|
|
|
|
|
| |
peoples code with irrelevant changes[1]:
Use bus_{read|write_*() instead of bus_space_{read|write}_*() for
purely stylistic reasons.
Due to compiler optimizations and inlining, this is for all practical
purposes without effect in the compiled code.
[1] NB: Approved by: sos
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
instead of writing apologetic comments. As it turns out, I need every
kernel page table page to have a legitimate pindex to support superpage
promotion on kernel memory.
Correct a nearby style error: Pointers should be compared to NULL.
|
|
|
|
|
|
|
|
| |
queues lock is acquired. Otherwise, the state of a reservation's
pages' flags and its population count can be inconsistent. That could
result in a page being freed twice.
Reported by: kris
|