diff options
author | We-unite <3205135446@qq.com> | 2024-07-18 14:28:52 +0800 |
---|---|---|
committer | We-unite <3205135446@qq.com> | 2024-07-18 18:59:19 +0800 |
commit | 58b1af7139bd2c4a2682382261fcc545b86d8685 (patch) | |
tree | abf0092fc69aa899935dcc08bf886dac5deb12cb /.gitignore | |
parent | f055b3940f999c2e26448812e67b68da363dcbad (diff) | |
download | godo-58b1af7139bd2c4a2682382261fcc545b86d8685.tar.gz godo-58b1af7139bd2c4a2682382261fcc545b86d8685.zip |
Mainly finish the second coroutine, organize event
As is planed, the first coroutine throw rae event infomation to the
second, and it organizes all info for the same event accroding to
event id, which is unique without shutdown of this computer.
There's several defficuties I've encountered, so I list their solution
here to remeber:
- raw info from 1st coroutine is correct, but wrong when 2nd gets it;
or it's correct while recieved, then regular expr goes to match it,
the first match is inline with expectations, but the next match goes
totally wrong, and the info is different from what is received.
Look into the src of go-libaudit, we'll find out that when heard
from netlink socket, the read buffer is always the same slice, it
first received a long data, then **pass the origin slice to
rawEvent.Data**, and then received a shorter data. rawEvent.Data is
passed to 2nd coruntine as **a pointer to rawEvent**, which means
all this 3 process use the same part of memory. Then, when a shorter
info comes from socket, the slice won't be moved, otherwise it write
aigin to this part of mem, then coroutine 2 will get a dirty data.
To deal with it, we change the type of channel from pointer to
interface, and make a deep copy of rawEvent before passing down.
As a result, the 2nd coroutine gets a copy of message but not origin,
it finally comes right.
- While designing a regular expr, it's thought correct but miss
matched from the right string. There maybe sth wrong that can't be
discovered by people's eye, you can try to rewrite the expr, then
it may be fixed.
Also, there's some hidden dangers:
- 2nd coroutine comes with no error checks althouth err variable is
set and catched ubder the rules of compiler. we **shall** make it
later.
- Is it reasonable to pass cooked event info immediately to 3rd
coroutine without waiting some time? Info from network is out of
order after all.
Fight! Fight! Fight!
Diffstat (limited to '.gitignore')
-rw-r--r-- | .gitignore | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -1,2 +1,3 @@ | |||
1 | .vscode/* | 1 | .vscode/* |
2 | godo \ No newline at end of file | 2 | godo |
3 | |||