Entware Pi-hole directly on the router? Yes!

[ColinTaylor]

It seems if the taint happens once, then the kernel knows it's tainted. At least that's what is out there in other explanations. But why does this kernel have to announce the taint at every turn spamming the log with all those messages?



It's puzzling that PiHole cannot invoke these kernel functions from the regular kernel code, and needs something that comes from a proprietary module somewhere. I would understand if this was some fancy functionality, but the regular shared memory stuff?

You're not understanding what RMerlin said. The entire kernel is tainted (and always will be) because it contains proprietary and out-of-tree modules. Ignore the word "Tainted", that's irrelevant. It's just one small part of the dumped information.

Aug 15 15:55:57 RT-AC86U-9988 kernel: pihole-FTL[37573]: syscall 403
Aug 15 15:55:57 RT-AC86U-9988 kernel: Code: 4620d02f f2404629 463a1393 df00461f (f1104617)
Aug 15 15:55:57 RT-AC86U-9988 kernel: CPU: 1 PID: 37573 Comm: pihole-FTL Tainted: P           O    4.1.27 #2
Aug 15 15:55:57 RT-AC86U-9988 kernel: Hardware name: Broadcom-v8A (DT)
Aug 15 15:55:57 RT-AC86U-9988 kernel: task: ffffffc0173b4080 ti: ffffffc01e86c000 task.ti: ffffffc01e86c000
Aug 15 15:55:57 RT-AC86U-9988 kernel: PC is at 0x2f3520
Aug 15 15:55:57 RT-AC86U-9988 kernel: LR is at 0x2f4349
Aug 15 15:55:57 RT-AC86U-9988 kernel: pc : [<00000000002f3520>] lr : [<00000000002f4349>] pstate: 60000030
Aug 15 15:55:57 RT-AC86U-9988 kernel: sp : 00000000fff07f60
Aug 15 15:55:57 RT-AC86U-9988 kernel: x12: 0000000000367bac
Aug 15 15:55:57 RT-AC86U-9988 kernel: x11: 0000000000000000 x10: 0000000000000000
Aug 15 15:55:57 RT-AC86U-9988 kernel: x9 : 0000000000302600 x8 : 0000000000000000
Aug 15 15:55:57 RT-AC86U-9988 kernel: x7 : 0000000000000193 x6 : 000000000001015d
Aug 15 15:55:57 RT-AC86U-9988 kernel: x5 : 00000000fff07f78 x4 : 0000000000000000
Aug 15 15:55:57 RT-AC86U-9988 kernel: x3 : 0000000000000193 x2 : 00000000fff07fa8
Aug 15 15:55:57 RT-AC86U-9988 kernel: x1 : 00000000fff07f78 x0 : 0000000000000000

 

[jacklul]

It's puzzling that PiHole cannot invoke these kernel functions from the regular kernel code, and needs something that comes from a proprietary module somewhere. I would understand if this was some fancy functionality, but the regular shared memory stuff?

One of the proprietary modules might be wrapping around those functions, I'm not an expert here.

 

[bibikalka]

You're not understanding what RMerlin said. The entire kernel is tainted (and always will be) because it contains proprietary and out-of-tree modules. Ignore the word "Tainted", that's irrelevant. It's just one small part of the dumped information.
...

OK, fair enough. But what is that all other info it's dumping? It does not appear to claim that there is an error, at least, no explicit messages to that effect.

 

[bibikalka]

One of the proprietary modules might be wrapping around those functions, I'm not an expert here.

It is a bit unfortunate to see so much output in the log due to this proprietary modules issue. So sounds like I shall continue filtering those messages via a custom filter:

# cat /opt/etc/syslog-ng.d/bcm_err_vA

filter z_bcm_err {
    ( program("kernel") and
    ( message("^x[0-9]") or
     message("^PC") or
     message("^LR") or
     message("^pc") or
     message("^sp") or
     message("^task") or
     message("^Code:") or
     message("^CPU:") or
     message("^dig") or
     message("^DROP") or
     message("^'\[00000000\]") or
     message("potentially") or
     message("pgd") or
     message("send_redir_page") or
     message("bcm_mcast_mld_add") or
     message("already exist in UDB") or
     message("not mesh client") or
     message("syscall") or
     message("^Hardware")) );
};

log {
    source(src);
    filter(z_bcm_err);
    flags(final);
};

#eof

 

[ColinTaylor]

OK, fair enough. But what is that all other info it's dumping? It does not appear to claim that there is an error, at least, no explicit messages to that effect.

The error is in the first line, e.g. "syscall 403". The PID and program name is on the third line. The rest of the information is probably of no use to you unless you're running the program in a debugging environment.