Re: [Weekly meetings] MoM - 13th of May 2021

[Mat Martineau <mathew.j.martineau@linux.intel.com>]

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]


On Thu, 13 May 2021, Matthieu Baerts wrote:

> Extra tests:
>    - news about Syzkaller? (Christoph):
>        - no new issues
>        - Mat is running a new Syzkaller instance for when Christoph is
> not available
>        - some syscalls are ignored:
>            - "disable_syscalls": ["perf_event_open", "syz_mount_image",
> "syz_read_part_table", "openat$ttyprintk", "mount", "mkdir",
> "openat$ptmx", "mq_open", "fsetxattr", "rt_tgsigqueueinfo",
> "ioctl$VT_RESIZE", "ioctl$TIOCVHANGUP", "get_robust_list",
> "openat$nullb", "ioctl$SCSI_IOCTL_SEND_COMMAND", "lremovexattr",
> "mknod$loop", "write$binfmt_script", "syz_open_dev$sg", "write$nbd",
> "prlimit64", "write$P9_RRENAMEAT", "fcntl$addseals", "finit_module",
> "ioctl$KDSETMODE", "write$FUSE_NOTIFY_STORE", "ioctl$TIOC
>                - *@Christoph* will send the rest on the ML
>            - not all debug options needs to be turned on otherwise it
> is too slow → share ideal .config?
>            - Could be good to have a dedicated Wiki page about that

I added a 'Testing' page to our wiki with information about kselftests, 
syzkaller, and packetdrill:

https://github.com/multipath-tcp/mptcp_net-next/wiki/Testing

There's a lot more information there about syzkaller than the other tools, 
but syzkaller is more complex to set up so I suppose that's natural. It's 
a wiki so we can add more information as needed!

--
Mat Martineau
Intel