From: "Nikolai Kondrashov" <Nikolai.Kondrashov@redhat.com>
To: Vishal Bhoj <vishal.bhoj@linaro.org>,
Nikolai Kondrashov <spbnick@gmail.com>
Cc: tuxsuite <tuxsuite@linaro.org>,
syzkaller <syzkaller@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>,
kernelci@groups.io
Subject: Re: Syzbot sends URLs in config names to KCIDB
Date: Sat, 18 Sep 2021 08:10:54 +0300 [thread overview]
Message-ID: <d950070e-29e7-0e81-c2ee-08edde2f1dc6@redhat.com> (raw)
In-Reply-To: <CAKdWgSzy85kG-sedQiCBKRADwV_C2EP1j4B6U6ypRFB7Rjw=oA@mail.gmail.com>
On 9/17/21 10:53 PM, Vishal Bhoj wrote:
> Hi Nick,
>
>
> On Fri, 17 Sept 2021 at 21:28, Nikolai Kondrashov <spbnick@gmail.com
> <mailto:spbnick@gmail.com>> wrote:
>
> On 9/17/21 6:49 PM, Dmitry Vyukov via groups.io <http://groups.io> wrote:
> > On Fri, 17 Sept 2021 at 17:45, Nikolai Kondrashov
> > <Nikolai.Kondrashov@redhat.com <mailto:Nikolai.Kondrashov@redhat.com>>
> wrote:
> >>
> >> Hi Dmitry,
> >>
> >> I've just noticed, but Syzbot has been sending URLs in build "config_name"
> >> fields for a while (see attached example), whereas the field is
> intended for a
> >> descriptive, human-readable name instead.
> >>
> >> Do you think you could fix that?
> >>
> >> Thank you.
> >> Nick
> >
> > Hi Nick,
> >
> > The attached info does not look like info from syzbot. It does not use
> > tuxbuild. That's somebody else.
>
> My bad, Friday evening got the best of me, sorry 🤦♂️
>
> That's coming from Tuxsuite.
>
> Whoever is responsible for Tuxsuite at Linaro now,
> could you please take a look?
>
>
> Thanks for letting us know, I have fixed it at our end now. Do let me know if
> the data needs any improvement.
Looks good now! Thanks a lot, Vishal!
Nick
prev parent reply other threads:[~2021-09-18 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 15:45 Syzbot sends URLs in config names to KCIDB Nikolai Kondrashov
2021-09-17 15:49 ` Dmitry Vyukov
2021-09-17 15:58 ` Nikolai Kondrashov
2021-09-17 19:53 ` Vishal
2021-09-18 5:10 ` Nikolai Kondrashov [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=d950070e-29e7-0e81-c2ee-08edde2f1dc6@redhat.com \
--to=nikolai.kondrashov@redhat.com \
--cc=dvyukov@google.com \
--cc=kernelci@groups.io \
--cc=spbnick@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=tuxsuite@linaro.org \
--cc=vishal.bhoj@linaro.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox