All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Christoph Paasch <cpaasch@apple.com>
Cc: mptcp@lists.linux.dev
Subject: Re: syzkaller config
Date: Thu, 13 May 2021 15:05:47 -0700 (PDT)	[thread overview]
Message-ID: <df27e284-9542-c2c2-dfaa-2ab6995c2653@linux.intel.com> (raw)
In-Reply-To: <YJ1IwGXK8aE2QCii@MacBook-Pro.local>

On Thu, 13 May 2021, Christoph Paasch wrote:

> Hello,
>
> this is my syzkaller config:
>
> {
>        "target": "linux/amd64",
>        "http": "127.0.0.1:56741",
>        "workdir": "/home/cpaasch/gopath/src/github.com/google/syzkaller/workdir_kasan_net",
>        "kernel_obj": "/mnt/tmp/build/",
>        "kernel_src": "/mnt/tmp/mptcp_syzkaller/",
>        "kernel_build_src": "/mnt/tmp/mptcp_syzkaller/",
>        "image": "/home/cpaasch/syzkaller/tools/stretch.img",
>        "sshkey": "/home/cpaasch/syzkaller/tools/stretch.id_rsa",
>        "syzkaller": "/home/cpaasch/gopath/src/github.com/google/syzkaller",
>        "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$TIOCL_SETVESABLANK", "fsmount", "socket$vsock_stream", "socketpair$unix", "socket$nl_audit", "connect$unix", "bind$unix"],
>        "procs": 8,
>        "type": "qemu",
>        "vm": {
>                "count": 24,

You're using a much bigger system than me :)

>                "kernel": "/mnt/tmp/build/arch/x86/boot/bzImage",
>                "cpu": 2,
>                "mem": 4096
>        }
> }
>
>
> The way I generate this list of disabled syscals is simply over time, when I
> saw that syzkaller was spending all of its efforts in those syscalls, I
> added it to the disable-list. That way now it is spending more time in
> MPTCP/networking related code.

I based the sample config in 
https://github.com/multipath-tcp/mptcp_net-next/wiki/Testing#syzkaller on 
this (with a couple of adjustments and some anonymization). Thanks for 
sharing.

--
Mat Martineau
Intel

      reply	other threads:[~2021-05-13 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13 15:41 syzkaller config Christoph Paasch
2021-05-13 22:05 ` Mat Martineau [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=df27e284-9542-c2c2-dfaa-2ab6995c2653@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=cpaasch@apple.com \
    --cc=mptcp@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.