-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Kernel crash: BTRFS on LUKS encrypted partition #350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Does this work on 3.9 or 3.6 kernels? |
It works on 3.6 and 3.9 kernels without problems. |
Sounds like an upstream bug. Might be worth searching for others with the same problem, or keep an eye out for updates to 3.10 kernel tree. |
Just checked this scenario on x86 platform and everything works fine. |
@kirgene do you still experience this issue? If not, please close this issue. Thanks. |
Add a test case to assert that the skb->pkt_type which was set from the BPF program is retained from the netkit xmit side to the peer's device at tcx ingress location. # ./vmtest.sh -- ./test_progs -t netkit [...] ./test_progs -t netkit [ 1.140780] bpf_testmod: loading out-of-tree module taints kernel. [ 1.141127] bpf_testmod: module verification failed: signature and/or required key missing - tainting kernel [ 1.284601] tsc: Refined TSC clocksource calibration: 3408.006 MHz [ 1.286672] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x311fd9b189d, max_idle_ns: 440795225691 ns [ 1.290384] clocksource: Switched to clocksource tsc #345 tc_netkit_basic:OK #346 tc_netkit_device:OK #347 tc_netkit_multi_links:OK #348 tc_netkit_multi_opts:OK #349 tc_netkit_neigh_links:OK #350 tc_netkit_pkt_type:OK Summary: 6/0 PASSED, 0 SKIPPED, 0 FAILED Signed-off-by: Daniel Borkmann <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Alexei Starovoitov <[email protected]>
I'm using kernel 3.10.4 (revision 9ab62f0).
Also I have LUKS encrypted BTRFS rootfs partition.
But when I boot my Pi I'm getting kernel crash (the image is attached).

The text was updated successfully, but these errors were encountered: