| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
- check hdr_size to make sure it is in the expected range
from sizeof entry_v1 to entry (entry_v4).
- alter msg() method to report NULL on invalid hdr_size
- alter all users of msg() method.
Bug: 30947841
Change-Id: I9bc1740d7aa9f37df5be966c18de1fb9de63d5dd
|
|
|
|
|
|
|
|
|
|
| |
Allow socket send syscall to terminate after 32 seconds if reader
stalled because of memory pressure allocating new network buffers
Add a gTest to catch regressions, add security buffer to log_dump
Bug: 27242723
Change-Id: Idaa6699d9d284e7f5f723ae0e76b3d6aa3371489
|
|
|
|
|
|
|
| |
Behavior is modified now, so react by fortifying the tests
Bug: 26447386
Change-Id: I6295783a0bc75282499aeba503a86bdb846908b5
|
|
|
|
| |
Change-Id: I1ccf49809b8a0a125601bdb52834c463e2d94165
|
|
|
|
| |
Change-Id: I8dd605452f1fef7706a627eedc251e39bb2e34cc
|
|
|
|
|
|
|
| |
Accepting a new lower standard of performance due to
the realities of the background cgroup.
Change-Id: Icd85050ffbf7f0129dd4c053323faedd0ff74048
|
|
|
|
|
|
|
|
| |
Add parsing to recognize optional chatty effective
percentage field as reported in the logger statistics.
Bug: 22855208
Change-Id: Id9c5e4a907ed0f9319beb9ddbfa27f4844bffc7d
|
|
|
|
|
|
|
| |
This is not the kernel logger you are looking for
Bug: 22787659
Change-Id: Idbf8fae908287ae9a96007b6353ec56d3c49f5bf
|
|
|
|
|
| |
Bug: 19603976
Change-Id: Ie920c128e7e6a436fea7a96c7d68bc39e13a2ad4
|
|
|
|
| |
Change-Id: I720b8ef1050da45a7833adef8219b6acb2cf3a38
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This forward port reverts
commit e457b74ce6ee6d799812dc2ec5e4b8b18bcd3e91
No longer as necessary once we add
liblog: Instrument logging of logd write drops
Although this provided an indication of how close statistically we
were to overloading logd it is simpler to understand fails thus to
hunt and peck a corrected value for /proc/sys/net/unix/max_dgram_qlen
Change-Id: I2b30e0fc30625a48fd11a12c2d2cc6a41f26226f
|
|
|
|
| |
Bug: 17409250
Change-Id: Id50ebb57754b12d69ed605d0e2901b8e05c607c6
|
|
|
|
|
| |
Bug: 15384806
Change-Id: I3072d6dd0618fa9ebe151c78a85eb121327f9df3
|
|
|
|
| |
Change-Id: I759c65e869d0c7cd81063fa7993ba3d67ef9cd06
|
|
|
|
|
|
|
|
| |
- Correct default tense for kernel or user logger
- harden code that parses the benchmark data
- give more meaning to the spam filter test
Change-Id: I97699037ca9d56718f53f08d22be79092fb431de
|
|
|
|
|
|
| |
- Deal with some -Wunused / -Wunused-variable issues
Change-Id: Ic86cd7b0680868ad0536198b71a34cb19134fc21
|
|
|
|
| |
Change-Id: Ie9c7a744e341e6e64afa14973d4d095717c97933
|
|
|
|
|
|
|
|
|
|
|
| |
- if network read/write broken up, reassemble the pieces.
- Use a 20ms poll to check if a new fragment has been
sent by the other side.
- fixup logd-unit-tests to take a (simplified) fragment
from the liblog changes.
Bug: 14164765
Change-Id: I98ff87888c119e1e8349717646d0f733e8971bc8
|
|
|
|
| |
Change-Id: Iea453764a1a4fc1661f461f10c641c30150e4d20
|
|
* Test statistics output, all four main log id types
are checked to be present, and output is properly
formatted with header (ascii new-line terminated
byte count) and trailer (newline formfeed) frames.
* On dev build test dgram_qlen, circumvent if
liblog benchmarks executed first though.
* Test if kernel and user space loggers are
present, and if any content has leaked to both.
* test benchmark and use it to verify worst UID pruning
Change-Id: I890c89f64825956f40108de806ed750b0170ac6c
|