| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
The reasoning behind this, is that if we are consistent in our
documentation about the uint*_t stuff, people will be less tempted to
write new code that uses the non-standard types.
I am not going to bump the man page dates, as these changes can be
considered style nits. The meaning of the man pages is unaffected.
MFC after: 1 month
|
|
|
|
| |
Approved by: philip (mentor)
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
r212438, repectively.
Approved by: keramida (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
PR: 150030
Submitted by: Janne Snabb snabb at epipe com
Patch by: Janne Snabb
Approved by: keramida (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fix mostly matters after r206129 that made it possible for
st_blksize to be greater than 4K. For this reason, this change should
be MFC-ed before r206129.
Also, it seems that all FreeBSD uitlities that use db(3) hash databases
and create new databases in files, specify their own block size value
and thus do not depend on block size autotuning.
PR: bin/144446
Submitted by: Peter Jeremy <peterjeremy@acm.org>
MFC after: 5 days
|
|
|
|
|
|
| |
PR: bin/144446
Submitted by: Peter Jeremy <peterjeremy@acm.org>
MFC after: 3 days
|
|
|
|
|
| |
a historical behavior that has been changed by revision 190491, and has seen
to break exim.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This does not include the new hash routines since they will cause problems
when reading old hash files.
Since mpool(3) has been changed, provide a compatibility shim for older
binaries.
Obtained from: OpenBSD
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
|
|
|
|
| |
open(). The previous logic only initializes the database when O_CREAT is
set, but as long as we can open and write the database, and the database
is empty, we should initialize it anyway.
Obtained from: OpenBSD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
an invariant (actually, an ugly hack) to fail, and all Hell would break
loose.
When deleting a big key, the offset of an empty page should be bsize, not
bsize-1; otherwise an insertion into the empty page will cause the new key to
be elongated by 1 byte.
Make the packing more dense in a couple of cases.
- fix NULL dereference exposed on big bsize values;
Obtained from: NetBSD via OpenBSD
|
|
|
|
|
|
| |
information.
Obtained from: OpenBSD
|
|
|
|
|
|
|
| |
LRU page.
- Fix for sequential retrieval failure when using large key/data pairs.
Obtained from: OpenBSD
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
|
|
| |
pairs, not onto a page containing the end of a big pair.
Obtained from: NetBSD via OpenBSD
|
| |
|
|
|
|
|
|
| |
in one more case.
Obtained from: NetBSD via OpenBSD
|
|
|
|
| |
Obtained from: NetBSD via OpenBSD
|
|
|
|
|
|
|
|
|
| |
if the result is truncated.
db/hash/hash_page.c: use the same way to create temporary file as
bt_open.c; check snprintf() return value.
Obtained from: OpenBSD
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
all; before freeing memory, zero out them before we release it as free
heap. This will eliminate some potential information leak issue.
While there, remove the PURIFY option. There is a slight difference between
the new behavior and the old -DPURIFY behavior, with the latter initializes
memory with 0xff's. The difference between old and new approach does not
generate observable difference.
Obtained from: OpenBSD (partly).
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
| |
Obtained from: NetBSD via OpenBSD
|
|
|
|
|
|
| |
malloc(3) call, so don't test if a pointer is NULL.
Obtained from: OpenBSD (in spirit)
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
| |
commit does not affect MD5 of object file.
|
|
|
|
|
|
|
| |
this commit does not affect any object code.
Obtained from: OpenBSD
Verified with: md5(1)
|
|
|
|
|
|
|
|
| |
(This is part of a larger changeset which is intended to reduce diff only,
thus some prototypes were left intact since they will be changed in the
future).
Verified with: md5(1)
|
|
|
|
|
| |
PR: docs/129400
Submitted by: Gavin Atkinson <gavin@freebsd.org>
|
| |
|
|
|
|
|
| |
the internal interface instead of casting away the constant
constraint upon calling.
|
| |
|
|
|
|
|
|
| |
clause.
# If I've done so improperly on a file, please let me know.
|
|
|
|
|
|
| |
PR: docs/80070
Submitted by: Aleksej Saushev
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Reviewed by: davidxu
|
| |
|
| |
|
|
|
|
|
|
| |
place during a split.
Obtained from: NetBSD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
caused by refering broken (uninitialized?) pointer which is retrieved
from __bt_new() (and from mpool_new()).
I don't know why this linp[0] is read before stored because this
should be controlled by .lower and .upper member of PAGE structure
which are correctly initialized.
But this workaround fixes the problem on my environment and this
module has #ifdef PURIFY option which initializes new and reused
memory from mpool by memset(p, 0xff, size) like as I did.
Please feel free to fix the real bug instead of my workaround.
|
| |
|
|
|
|
|
|
|
|
|
| |
mpool_open(3) - it is *not* really used for synchronization; in fact,
it is not used at all.
PR: 70929
Submitted by: Martin Kammerhofer <dada@sbox.tugraz.at>
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
instead of lseek()/_read() and lseek()/_write().
PR: bin/54276
Submitted by: <dnelson@allantgroup.com>
|
| |
|