All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandr Nogikh <nogikh@google.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Lee Jones <lee@kernel.org>,
	syzbot <syzbot+15cd994e273307bf5cfa@syzkaller.appspotmail.com>,
	adilger.kernel@dilger.ca, gregkh@linuxfoundation.org,
	lczerner@redhat.com, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, sashal@kernel.org,
	stable@vger.kernel.org, syzkaller-android-bugs@googlegroups.com,
	tadeusz.struk@linaro.org
Subject: Re: kernel BUG in ext4_free_blocks (2)
Date: Wed, 21 Dec 2022 12:34:23 +0100	[thread overview]
Message-ID: <CANp29Y7T+sG4JYkZttpyBkz54SUwOz=BhJED+QmKOGp2CgceiA@mail.gmail.com> (raw)
In-Reply-To: <Y6CqJ8fgQQW8AhT6@mit.edu>

On Mon, Dec 19, 2022 at 7:15 PM Theodore Ts'o <tytso@mit.edu> wrote:
>
< ... >
> It's not obvious what you mean by the "main page" of the namespace.
> I'm guessing, but from the bug report page, there is a horizontal set
> of icons, "Open", "Fixed", "Invalid" .... (which all have the same
> icons), that the "Open" icon is the one that gets to the main page?

Yes.

>
> Assuming that this[1] is what was meant by "main page" (which is also
> implied by the URL, but it's otherwise **really** not obvious), where
> is the list of tested trees?
>
> [1] https://syzkaller.appspot.com/android-5-10

I've just deployed the changes that add the page with the list of the
tested repositories as well as a link to it from the "main page" (look
above the table with instances). For Android, we indeed don't test
many trees:

https://syzkaller.appspot.com/android-5-10/repos

For Linux upstream, there are more trees:

https://syzkaller.appspot.com/upstream/repos

> At least for the android-5-10 namespace, why not just
> say, "I don't see that commit on the git branch <explicit git repo and
> branch name>"?

Now such email messages will include the kernel name and some of the
tested repositories (with the link to the full list page). E.g.
https://github.com/google/syzkaller/blob/4067838e6b16173af08e062ce434ecfc46d45bda/dashboard/app/notifications_test.go#L106

--
Aleksandr

  reply	other threads:[~2022-12-21 11:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0000000000006c411605e2f127e5@google.com>
2022-10-20 16:32 ` kernel BUG in ext4_free_blocks (2) syzbot
2022-11-03 16:33 ` syzbot
2022-11-17 16:34 ` syzbot
2022-12-01 16:34 ` syzbot
2022-12-15 16:34 ` syzbot
2022-12-16  2:11   ` Theodore Ts'o
2022-12-16 13:01     ` Lee Jones
2022-12-16 14:09       ` Aleksandr Nogikh
2022-12-16 14:12         ` Lee Jones
2022-12-16 17:04         ` Theodore Ts'o
2022-12-16 17:14           ` Aleksandr Nogikh
2022-12-16 18:45             ` Theodore Ts'o
2022-12-19 16:12               ` Aleksandr Nogikh
2022-12-19 18:15                 ` Theodore Ts'o
2022-12-21 11:34                   ` Aleksandr Nogikh [this message]
2023-01-04 11:34 ` syzbot
2023-01-18 12:45 ` syzbot
2023-02-01 12:45 ` syzbot
2023-02-15 12:45 ` [Android 5.10] " syzbot
2023-03-01 12:46 ` syzbot
2023-03-01 13:51   ` Tudor Ambarus

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='CANp29Y7T+sG4JYkZttpyBkz54SUwOz=BhJED+QmKOGp2CgceiA@mail.gmail.com' \
    --to=nogikh@google.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=lczerner@redhat.com \
    --cc=lee@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+15cd994e273307bf5cfa@syzkaller.appspotmail.com \
    --cc=syzkaller-android-bugs@googlegroups.com \
    --cc=tadeusz.struk@linaro.org \
    --cc=tytso@mit.edu \
    /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.