| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
extracted from tar archives. Otherwise, converting tar archives to
cpio format (with "bsdtar -cf out.cpio @in.tar") convert every entry
into a hard link to a single file. This simple logic breaks hard
links, but that's better than the alternative.
MFC after: 7 days
|
|
|
|
|
|
|
|
| |
header of the pax extension entry, clip them to ustar limits. In particular,
this prevents an internal panic for very old files.
Thanks to: Chris Spiegel
MFC after: 7 days
|
|
|
|
|
|
|
|
| |
GNU tar sparse files, people have extended cpio) and clarify an
important detail about pax format (that ustar-compliant archivers
can mostly read pax archives correctly).
MFC after: 7 days
|
|
|
|
|
|
|
|
|
|
|
|
| |
that knows how to extract UMA(9) allocator statistics from a core dump or
live memory image using kvm(3). The caller is expected to provide the
necessary kvm_t handle, which is then used by libmemstat(3).
With these changes, it is trivially straight forward to re-introduce
vmstat -z support on core dumps, which was lost when UMA was introduced.
In the short term, this requires including vm/ include files that are not
intended for extra-kernel use, requiring in turn some ugliness.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Move memory_type_list flushing logic from memstat_mtl_free() to
_memstat_mtl_empty(), a libmemstat-internal function that can
be called from other parts of the library. Invoke
_memstat_mtl_empty() from memstat_mtl_free(), which also frees
the containing list structure.
Invoke _memstat_mtl_empty() instead of memstat_mtl_free() in
various error cases in memstat_malloc.c and memstat_uma.c, which
previously resulted in the list being freed prematurely.
- Reverse the order of updating the mt_kegfree and mt_free fields
of the memory_type in memstat_uma.c, otherwise keg free items
won't be counted properly for non-secondary zones.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
that have at least 3 characters.
MFC after: 1 week
Thanks to: Music band ``Chingon''
for keeping me company while searching for these.
|
| |
|
| |
|
| |
|
|
|
|
| |
the recent atomic_ptr() change.
|
|
|
|
|
|
| |
PR: bin/84106
Obtained from: BIND9
MFC after: 2 days
|
|
|
|
|
|
|
|
|
| |
carefully crafted deflated data stream. [1]
Correct problems in the AES-XCBC-MAC IPsec authentication algorithm. [2]
Submitted by: suz [2]
Security: FreeBSD-SA-05:18.zlib [1], FreeBSD-SA-05:19.ipsec [2]
|
|
|
|
|
|
|
| |
avoid overwriting ty_status values set from the 'type' field.
Previously TTY_DIALUP and TTY_NETWORK flags did not match
specified type.
|
|
|
|
|
|
|
|
| |
than increase it, and seems to be the cause of the memory leaks which some
users have reported.
Requested by: dougb
MFC after: 5 days
|
|
|
|
|
|
|
| |
as they actually belong to the primary zone, and maye otherwise be
reported more than once.
MFC after: 1 day
|
|
|
|
|
| |
- use wcsrtombs() instead of a wcrtomb() loop where possible.
- avoid wcrtomb() loop when output precision is small.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
conversion routine, now change my mind and add one, memstat_strerror(3),
which returns a const char * pointer to a string describing the error,
to be used on the results of memstat_mtl_geterror().
While here, also correct a minor typo in the HISTORY man page.
Pointers on improving ease of internationalization would be
appreciated.
MFC after: 1 day
|
|
|
|
|
|
|
|
| |
- Short description of each memory type access method.
- Descriptions of libmemstat(3) errors and memstat_mtl_geterror(3).
MFC after: 1 day
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Define a set of libmemstat(3) error constants, which are used by all
libmemstat(3) methods except for memstat_mtl_alloc(), which allocates
a memory type list and may return ENOMEM via errno.
- Define a per-memory_type_list current error value, which is set when a
call associated with a memory list fails. This requires wrapping a
structure around the queue(9) list head data structure, but this change
is not visible to libmemstat(3) consumers due to using access methods.
- Add a new accessor method, memstat_mtl_geterror() to retrieve the error
number.
- Consistently set the error number in a number of failure modes where
previously some combination of setting errno and printf'ing error
descriptions was used. libmemstat(3) will now no longer print to stdio
under any circumstances. Returns of NULL/-1 for errors remain the
same.
This avoids use of stdio, misuse of error numbers, and should make it
easier to program a libmemstat(3) consumer able to print useful error
messages. Currently, no error-to-string function is provided, as I'm
unsure how to address internationalization concerns.
MFC after: 1 day
|
| |
|
|
|
|
|
|
|
| |
try and discourage use outside the library.
Remove duplicate declaration of memstat_mtl_free() from memstat_internal.h,
as it's not internal, and the memstat.h definition suffices.
|
|
|
|
|
|
|
| |
matching is used.
PR: 35506
MFC after: 3 days
|
|
|
|
|
| |
from struct addrinfo. This change break ABI compatibility
on 64 bit arch.
|
|
|
|
|
|
|
| |
been bumped since RELENG_5.
Reviewed by: ru
Approved by: re (not needed for commit check but in principle...)
|
| |
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
| |
HISTORY section.
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on top of a primary zone, sharing the same allocation "keg". When
reporting statistics for zones, do not report the free items in the
keg as part of the free items in the zone, or those free items will
be reported more than once: for the primary zone, and then any
secondary zones off the primary zone. Separately record and maintain
a kegfree statistic, and export via memstat_get_kegfree(), which is
available for use if needed. Since items free'd back to the keg are
not fully initialized, and hence may not actually be available (since
secondary zone ctor-time initialization can fail), this makes some
amount of sense.
This change corrects a bug made visible in the libmemstat(3)
modifications to netstat: mbufs freed back to the keg from the
packet zone would be counted twice, resulting in negative values
being printed in the mbuf free count.
Some further refinement of reporting relating to secondary zones may
still be required.
Reported by: ssouhlal
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Keiichi SHIMA <keiichi__at__iijlab.net>
Obtained from: KAME
|
|
|
|
|
|
|
| |
reported by Delia Kecskemeti <delia.kecskemeti__at__windriver.com>
Submitted by: Keiichi SHIMA <keiichi__at__iijlab.net>
Obtained from: KAME
|
|
|
|
|
|
|
|
| |
long time... i.e. since this file was imported... (ufs1 supports much
larger files then this)...
Submitted by: Ivan Voras
MFC after: 1 week
|
|
|
|
|
|
|
| |
consume that many slots to track snapshot-to-snapshot changes and
running totals. And 16 is a nice round number.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
|
| |
functions and must now be either an unsigned char or EOF, regardless of
locale.
|
|
|
|
|
| |
and toupper() must now be either an unsigned char or EOF, regardless of
locale.
|
|
|
|
|
|
| |
Requested by: many Korean users from bsdforum.or.kr
Submitted by: perky
Approved by: anholt (mentor)
|
|
|
|
|
| |
Requested by: victor cruceru <victor dot cruceru at gmail dot com>
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
replaces any previous mapping to the same address.
Obtained from: IEEE Std 1003.1, 2004 Edition
|
|
|
|
|
|
| |
as well as documenting MEMSTAT_MAXCALLER.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
MEMSTAT_MAXCALLER (8), and expose MEMSTAT_MAXCALLER via memstat.h so
that applications can check their assumptions about how many slots
are available.
Remove 'spare' memory storage in struct malloc_type, since we now
don't expose the data structure internals to applications and rely
on accessor methods, this approach to ABI stability isn't required.
MFC after: 7 days
|
|
|
|
|
|
| |
memstat_mtl_find().
MFC after: 10 days
|
|
|
|
|
| |
Submitted by: jkoshy
MFC after: 1 week
|
|
|
|
|
|
|
| |
- Change some section numbers to match reality
- For MLINKS to manpages from ports, mention which port installs them
MFC after: 3 days
|
|
|
|
|
|
| |
global counters maintained in the zone.
MFC after: 1 week
|
| |
|