All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com>
To: miklos@szeredi.hu
Cc: linux-integrity@vger.kernel.org, linux-unionfs@vger.kernel.org,
	miklos@szeredi.hu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in mnt_want_write (2)
Date: Tue, 06 Jun 2023 02:12:36 -0700	[thread overview]
Message-ID: <00000000000090dbc405fd726b57@google.com> (raw)
In-Reply-To: <CAJfpegtzZnzW506AHyw_5Bqn-thhrd3-_t-qJ5OJBzP-z3O6Fg@mail.gmail.com>

> #syz set subsystems: intergrity, overlayfs

The specified label value is incorrect.
"intergrity" is not among the allowed values.
Please use one of the supported label values.

The following labels are suported:
missing-backport, no-reminders, prio: {low, normal, high}, subsystems: {.. see below ..}
The list of subsystems: https://syzkaller.appspot.com/upstream/subsystems?all=true


  reply	other threads:[~2023-06-06  9:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 16:59 [syzbot] possible deadlock in mnt_want_write (2) syzbot
2021-07-19 15:11 ` Miklos Szeredi
2021-07-22 13:50   ` Mimi Zohar
2022-07-02 17:27 ` syzbot
2022-07-05 12:53   ` Mimi Zohar
2022-07-06 12:10     ` Hillf Danton
2022-07-06 22:24       ` Mimi Zohar
2023-06-06  9:12 ` Miklos Szeredi
2023-06-06  9:12   ` syzbot [this message]
2023-06-06  9:13     ` Miklos Szeredi
2023-10-04 16:45 ` [syzbot] [integrity] [overlayfs] " syzbot
2023-10-05  9:36   ` Amir Goldstein
2023-10-05  9:59     ` syzbot
2023-10-05 10:26       ` Amir Goldstein
2023-10-05 10:46         ` syzbot
2023-10-05 11:47         ` Mimi Zohar
2023-10-05 13:22           ` Amir Goldstein
2023-10-05 13:35             ` Mimi Zohar
     [not found] <20220703013354.1025-1-hdanton@sina.com>
2022-07-03  6:42 ` [syzbot] " syzbot
     [not found] <20220703070714.1237-1-hdanton@sina.com>
2022-07-03  7:40 ` syzbot

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=00000000000090dbc405fd726b57@google.com \
    --to=syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=syzkaller-bugs@googlegroups.com \
    /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.