> -----Original Message----- > From: Kees Cook [mailto:keescook@xxxxxxxxxxxx] > Sent: Friday, November 30, 2018 10:58 AM > To: Liu, Wenlong/刘 文龙 <liuwl.fnst@xxxxxxxxxxxxxx> > Cc: Andy Lutomirski <luto@xxxxxxxxxxxxxx>; Will Drewry > <wad@xxxxxxxxxxxx>; Shuah Khan <shuah@xxxxxxxxxx>; open list:KERNEL > SELFTEST FRAMEWORK <linux-kselftest@xxxxxxxxxxxxxxx>; > yuichi.kusakabe@xxxxxxxxxxxxx; kisuke.kawamura@xxxxxxxxxxxxx > Subject: Re: seccomp/seccomp_bpf: test terminated by the not expected > behavior > > --- > > Although I am not so familiar with SECCOMP and BPF, I checked some related > documents and codes. > > About the failures above, what the most confused me is that why it always > give ENOSYS. > > > > Am I missing something? > > Thanks in advance. > > > > PS: > > I didn't run "make kselftest-merge" before compiling the kernel that I'm > using. > > > > --- > > The Test Environment: > > - Kernel version: v4.14.0 > > Hi! > > It appears you're attempting to use a newer seccomp selftest on an older > kernel. That isn't a supported way to test seccomp. You'll need to build > 4.14's seccomp_bpf test binary and run it instead. Thanks for your reply. Indeed, there is little difference between the version of kernel and kselftest. Someone(or doc) tells me that, If you run a kernel xyz, then always run the BPF kernel selftests from that kernel xyz as well. Do not expect that the BPF selftest from the latest mainline tree will pass all the time. But I forget that, the little difference in my case is different "z". :-) My fault. Thanks again. Best regards Liu > -- > Kees Cook >
