From: Dmitry Vyukov
Date: Mon, 12 Mar 2018 09:56:42 +0100
> But I don't see kernelci.orgbot referenced anywhere in the emails.
> E.g. in the one that was linked above:
> https://groups.google.com/forum/message/raw?msg=syzkaller-bugs/OkwLGoS6UQA/hHAtCdnNBgAJ
I'm not referencing that one above, I'
On Thu, Mar 8, 2018 at 9:03 PM, David Miller wrote:
> From: Dmitry Vyukov
> Date: Thu, 1 Mar 2018 17:22:54 +0100
>
>> The problem strikes back.
>> Again people complain that a email does not appear on LKML:
>> https://www.spinics.net/lists/kernel/msg2735905.html
>> Though, it appeared on syzkalle
From: Dmitry Vyukov
Date: Thu, 1 Mar 2018 17:22:54 +0100
> The problem strikes back.
> Again people complain that a email does not appear on LKML:
> https://www.spinics.net/lists/kernel/msg2735905.html
> Though, it appeared on syzkaller-bugs group:
> https://groups.google.com/d/msg/syzkaller-bugs
On Thu, Jan 4, 2018 at 12:20 PM, Greg Kroah-Hartman
wrote:
>> > On Thu, Jan 04, 2018 at 10:09:16AM +0100, Dmitry Vyukov wrote:
>> > > Hello,
>> > >
>> > > Some of syzbot emails don't appear on LKML mailing lists, while they
>> > > were mailed as any other emails. Here are few examples:
>> > >
>> >
On Wed, Jan 24, 2018 at 11:06:02AM -0600, Eric W. Biederman wrote:
> Alan Cox writes:
>
> > On Tue, 16 Jan 2018 09:34:01 +0100
> > Dmitry Vyukov wrote:
> >
> >> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
> >> >> Outside of the bugs being considered as considered as security issues,
>
Alan Cox writes:
> On Tue, 16 Jan 2018 09:34:01 +0100
> Dmitry Vyukov wrote:
>
>> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
>> >> Outside of the bugs being considered as considered as security issues,
>> >> the bugs syzbot finds are generally things that don't affect anyone in
>> >>
On Tue, 16 Jan 2018 09:34:01 +0100
Dmitry Vyukov wrote:
> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
> >> Outside of the bugs being considered as considered as security issues,
> >> the bugs syzbot finds are generally things that don't affect anyone in
> >> practice. So are very low
On Wed, 2018-01-17 at 18:16 +0100, Dmitry Vyukov wrote:
[...]
> Agree, but as far as I understand it is specifically restricted. You
> can see docs here:
> https://cloud.google.com/appengine/docs/standard/php/mail/mail-with-headers-attachments
ROTFL - as if almost no one at Google know that there
On Wed, Jan 17, 2018 at 5:53 PM, Theodore Ts'o wrote:
> On Wed, Jan 17, 2018 at 09:06:54AM +0100, Dmitry Vyukov wrote:
>> I've also mailed a change to appengine that supports *.c, *.log and
>> *.patch as text/plain extensions. There does not seem to be any major
>> objects to it, but it will proba
On Wed, Jan 17, 2018 at 09:06:54AM +0100, Dmitry Vyukov wrote:
> I've also mailed a change to appengine that supports *.c, *.log and
> *.patch as text/plain extensions. There does not seem to be any major
> objects to it, but it will probably take some time to be deployed in
> prod. After that I wi
On Mon, Jan 15, 2018 at 5:38 PM, Eric W. Biederman
wrote:
> I am definitely not asking for expertise in the kernel. I am asking
> for a human who wants to help track down bugs in the kernel.
What is that additional information that you need and that syzbot
currently does not provide?
On Wed, Jan 17, 2018 at 12:13 AM, Theodore Ts'o wrote:
> On Tue, Jan 16, 2018 at 09:31:26AM +0100, Dmitry Vyukov wrote:
>> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
>> > I just checked a recent report from the Syzbot, and it's not fixed.
>> > The raw.log file still uses a Content-Type
On Tue, Jan 16, 2018 at 09:31:26AM +0100, Dmitry Vyukov wrote:
> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
> > I just checked a recent report from the Syzbot, and it's not fixed.
> > The raw.log file still uses a Content-Type of
> > Application/Octet-stream. Worse the reproducer C sou
On Mon, Jan 15, 2018 at 5:38 PM, Eric W. Biederman
wrote:
> When I made the complaint it came to me and to messages on lkml as
> .log. With Content-Type: Application/Octent-stream.
Where was that? If I am not mistaken you actually didn't. I
triple-checked my inbox and searched internet. The onl
On Mon, Jan 15, 2018 at 5:16 PM, Eric W. Biederman
wrote:
> Dmitry Vyukov writes:
>
> 2> On Mon, Jan 15, 2018 at 1:54 PM, Pavel Machek wrote:
>>> Hi!
>>>
> *Snort*
>
> If the information to solve an issue is not in the Oops syzbot is
> useless.
Hi Eric
Tha
On Tue, Jan 16, 2018 at 08:59:36AM +0100, Dmitry Vyukov wrote:
On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
On Mon, Jan 15, 2018 at 10:38:42AM -0600, Eric W. Biederman wrote:
Sometimes the branches on linux-next are experimental crap. If someone
adds an experimental memory allocator
On Tue, Jan 16, 2018 at 1:56 AM, Dmitry Vyukov wrote:
> On Tue, Jan 16, 2018 at 10:52 AM, Guenter Roeck wrote:
>> On Mon, Jan 15, 2018 at 11:51 PM, Dmitry Vyukov wrote:
>>> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
On Mon, Jan 15, 2018 at 10:38:42AM -0600, Eric W. Biederman wro
On Tue, Jan 16, 2018 at 10:52 AM, Guenter Roeck wrote:
> On Mon, Jan 15, 2018 at 11:51 PM, Dmitry Vyukov wrote:
>> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
>>> On Mon, Jan 15, 2018 at 10:38:42AM -0600, Eric W. Biederman wrote:
Sometimes the branches on linux-next are exper
On Mon, Jan 15, 2018 at 11:51 PM, Dmitry Vyukov wrote:
> On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
>> On Mon, Jan 15, 2018 at 10:38:42AM -0600, Eric W. Biederman wrote:
>>>
>>> Sometimes the branches on linux-next are experimental crap. If someone
>>> adds an experimental memory allo
On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
>> Outside of the bugs being considered as considered as security issues,
>> the bugs syzbot finds are generally things that don't affect anyone in
>> practice. So are very low on the priority of things to get fixed.
Not sure why are you sayi
On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
> I just checked a recent report from the Syzbot, and it's not fixed.
> The raw.log file still uses a Content-Type of
> Application/Octet-stream. Worse the reproducer C source file has a
> content type of Application/Octet-stream instead of th
On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
> On Mon, Jan 15, 2018 at 10:38:42AM -0600, Eric W. Biederman wrote:
>>
>> Sometimes the branches on linux-next are experimental crap. If someone
>> adds an experimental memory allocator to linux-next before discovering
>> it causes all kinds
On Tue, Jan 16, 2018 at 8:12 AM, Theodore Ts'o wrote:
> On Mon, Jan 15, 2018 at 10:38:42AM -0600, Eric W. Biederman wrote:
>>
>> Sometimes the branches on linux-next are experimental crap. If someone
>> adds an experimental memory allocator to linux-next before discovering
>> it causes all kinds
On Mon, Jan 15, 2018 at 10:38:42AM -0600, Eric W. Biederman wrote:
>
> Sometimes the branches on linux-next are experimental crap. If someone
> adds an experimental memory allocator to linux-next before discovering
> it causes all kinds of problems I don't want bug reports about my code
> not bei
Dmitry Vyukov writes:
> On Thu, Jan 4, 2018 at 4:23 PM, Eric W. Biederman
> wrote:
>> Dmitry Vyukov writes:
>>
>>> Hi Pavel,
>>>
>>> I've answered this question here in full detail. In short, this is
>>> useful and actionable.
>>> https://groups.google.com/d/msg/syzkaller/2nVn_XkVhEE/GjjfISejC
Dmitry Vyukov writes:
2> On Mon, Jan 15, 2018 at 1:54 PM, Pavel Machek wrote:
>> Hi!
>>
>>> > *Snort*
>>> >
>>> > If the information to solve an issue is not in the Oops syzbot is
>>> > useless.
>>>
>>> Hi Eric
>>>
>>> That's true. But maintainers of the subsystem is in the best position
>>> to
Hi!
> >> In lots of cases (~50%) quality of syzbot reports is equal to human
> >> reports, or _higher_.
> >> It provides exact kernel commit, config, compiler, stand-alone C
> >> reproducer and a nice, symbolized report even with inline frames. You
> >> don't always get all of this from human repo
On Mon, Jan 15, 2018 at 2:08 PM, Pavel Machek wrote:
> On Mon 2018-01-15 11:08:12, Dmitry Vyukov wrote:
>> On Thu, Jan 4, 2018 at 12:18 PM, Pavel Machek wrote:
>> > On Thu 2018-01-04 12:09:26, Dmitry Vyukov wrote:
>> >> On Thu, Jan 4, 2018 at 10:56 AM, Pavel Machek wrote:
>> >> >> On Thu, 2018-0
On Mon 2018-01-15 11:08:12, Dmitry Vyukov wrote:
> On Thu, Jan 4, 2018 at 12:18 PM, Pavel Machek wrote:
> > On Thu 2018-01-04 12:09:26, Dmitry Vyukov wrote:
> >> On Thu, Jan 4, 2018 at 10:56 AM, Pavel Machek wrote:
> >> >> On Thu, 2018-01-04 at 10:25 +0100, Pavel Machek wrote:
> >> >> > Hi!
> >>
On Mon, Jan 15, 2018 at 1:54 PM, Pavel Machek wrote:
> Hi!
>
>> > *Snort*
>> >
>> > If the information to solve an issue is not in the Oops syzbot is
>> > useless.
>>
>> Hi Eric
>>
>> That's true. But maintainers of the subsystem is in the best position
>> to judge that. For that they need to see
Hi!
> > *Snort*
> >
> > If the information to solve an issue is not in the Oops syzbot is
> > useless.
>
> Hi Eric
>
> That's true. But maintainers of the subsystem is in the best position
> to judge that. For that they need to see the report.
Unless they are already overloaded by better qualit
On Thu, Jan 4, 2018 at 4:23 PM, Eric W. Biederman wrote:
> Dmitry Vyukov writes:
>
>> Hi Pavel,
>>
>> I've answered this question here in full detail. In short, this is
>> useful and actionable.
>> https://groups.google.com/d/msg/syzkaller/2nVn_XkVhEE/GjjfISejCgAJ
>
> *Snort*
>
> If the informati
On Thu, Jan 4, 2018 at 12:18 PM, Pavel Machek wrote:
> On Thu 2018-01-04 12:09:26, Dmitry Vyukov wrote:
>> On Thu, Jan 4, 2018 at 10:56 AM, Pavel Machek wrote:
>> >> On Thu, 2018-01-04 at 10:25 +0100, Pavel Machek wrote:
>> >> > Hi!
>> >> > >
>> >> > > Some of syzbot emails don't appear on LKML m
On Thu, Jan 4, 2018 at 4:35 PM, David Miller wrote:
> From: Greg Kroah-Hartman
> Date: Thu, 4 Jan 2018 12:20:28 +0100
>
>> If no one can, then it's just a spam bot and if I were vger's
>> postmaster, I would blacklist it as well :)
>
> +1
Just to make it clear, humans were reading all normal co
On Fri, Jan 5, 2018 at 12:50 AM, Theodore Ts'o wrote:
> It also seems to me, looking at other complaints on this thread, that
> there is the opportunity for the syzbot to do much more. For example,
> you can see if it repro's on the last released mainline kernel (such
> as 4.14) and if so, have t
On Fri, Jan 5, 2018 at 12:50 AM, Theodore Ts'o wrote:
> On Thu, Jan 04, 2018 at 12:04:34PM +0100, Dmitry Vyukov wrote:
>>
>> The problem is that it's not _me_, it's a computer program which uses
>> some mail delivery system which I don't have full visibility into. I
>> don't know if it even gets b
On Thu, Jan 04, 2018 at 12:04:34PM +0100, Dmitry Vyukov wrote:
>
> The problem is that it's not _me_, it's a computer program which uses
> some mail delivery system which I don't have full visibility into. I
> don't know if it even gets bounce emails (as far as I understand it's
> not LKML that ge
On Thu 2018-01-04 12:09:26, Dmitry Vyukov wrote:
> On Thu, Jan 4, 2018 at 10:56 AM, Pavel Machek wrote:
> >> On Thu, 2018-01-04 at 10:25 +0100, Pavel Machek wrote:
> >> > Hi!
> >> > >
> >> > > Some of syzbot emails don't appear on LKML mailing lists, while they
> >> > > were mailed as any other em
04.01.2018, 18:31, "David Miller" :
> From: Ozgur
> Date: Thu, 04 Jan 2018 12:56:56 +0300
Dvyukov,
I think you will set a bot sensitive and syzbot send e-mail that it doesn't
disturb list members :)
David is sometimes nervous.
Ozgur
>> autoanswer is just automated reply address that the lmkl
From: Greg Kroah-Hartman
Date: Thu, 4 Jan 2018 12:20:28 +0100
> If no one can, then it's just a spam bot and if I were vger's
> postmaster, I would blacklist it as well :)
+1
From: Ozgur
Date: Thu, 04 Jan 2018 12:56:56 +0300
> autoanswer is just automated reply address that the lmkl system works and
> your email arrives.
> LKML e-mail list implemented SPF, DKIM and DMARC and I think some domains
> were forbid.
> For example yandex.ru or mail.ru
If I am given specif
Dmitry Vyukov writes:
> Hi Pavel,
>
> I've answered this question here in full detail. In short, this is
> useful and actionable.
> https://groups.google.com/d/msg/syzkaller/2nVn_XkVhEE/GjjfISejCgAJ
*Snort*
If the information to solve an issue is not in the Oops syzbot is
useless.
The Oops isn
On Thu, Jan 04, 2018 at 12:04:34PM +0100, Dmitry Vyukov wrote:
> On Thu, Jan 4, 2018 at 10:23 AM, Greg Kroah-Hartman
> wrote:
> >
> > On Thu, Jan 04, 2018 at 10:09:16AM +0100, Dmitry Vyukov wrote:
> > > Hello,
> > >
> > > Some of syzbot emails don't appear on LKML mailing lists, while they
> > > w
On Thu 2018-01-04 12:09:26, Dmitry Vyukov wrote:
> On Thu, Jan 4, 2018 at 10:56 AM, Pavel Machek wrote:
> >> On Thu, 2018-01-04 at 10:25 +0100, Pavel Machek wrote:
> >> > Hi!
> >> > >
> >> > > Some of syzbot emails don't appear on LKML mailing lists, while they
> >> > > were mailed as any other em
On Thu, Jan 4, 2018 at 10:56 AM, Pavel Machek wrote:
>> On Thu, 2018-01-04 at 10:25 +0100, Pavel Machek wrote:
>> > Hi!
>> > >
>> > > Some of syzbot emails don't appear on LKML mailing lists, while they
>> > > were mailed as any other emails. Here are few examples:
>> > >
>> > > "KASAN: use-after-
On Thu, Jan 4, 2018 at 10:23 AM, Greg Kroah-Hartman
wrote:
>
> On Thu, Jan 04, 2018 at 10:09:16AM +0100, Dmitry Vyukov wrote:
> > Hello,
> >
> > Some of syzbot emails don't appear on LKML mailing lists, while they
> > were mailed as any other emails. Here are few examples:
> >
> > "KASAN: use-afte
04.01.2018, 12:23, "Greg Kroah-Hartman" :
> On Thu, Jan 04, 2018 at 10:09:16AM +0100, Dmitry Vyukov wrote:
>> Hello,
>>
>> Some of syzbot emails don't appear on LKML mailing lists, while they
>> were mailed as any other emails. Here are few examples:
>>
>> "KASAN: use-after-free Read in rds_t
> On Thu, 2018-01-04 at 10:25 +0100, Pavel Machek wrote:
> > Hi!
> > >
> > > Some of syzbot emails don't appear on LKML mailing lists, while they
> > > were mailed as any other emails. Here are few examples:
> > >
> > > "KASAN: use-after-free Read in rds_tcp_dev_event"
> > > https://groups.google
On Thu, 2018-01-04 at 10:25 +0100, Pavel Machek wrote:
> Hi!
> >
> > Some of syzbot emails don't appear on LKML mailing lists, while they
> > were mailed as any other emails. Here are few examples:
> >
> > "KASAN: use-after-free Read in rds_tcp_dev_event"
> > https://groups.google.com/d/msg/syzka
Hi!
>
> Some of syzbot emails don't appear on LKML mailing lists, while they
> were mailed as any other emails. Here are few examples:
>
> "KASAN: use-after-free Read in rds_tcp_dev_event"
> https://groups.google.com/d/msg/syzkaller-bugs/nEeIAsNLWL4/1GzamOmRAwAJ
>
> "general protection fault in
On Thu, Jan 04, 2018 at 10:09:16AM +0100, Dmitry Vyukov wrote:
> Hello,
>
> Some of syzbot emails don't appear on LKML mailing lists, while they
> were mailed as any other emails. Here are few examples:
>
> "KASAN: use-after-free Read in rds_tcp_dev_event"
> https://groups.google.com/d/msg/syzkal
Hello,
Some of syzbot emails don't appear on LKML mailing lists, while they
were mailed as any other emails. Here are few examples:
"KASAN: use-after-free Read in rds_tcp_dev_event"
https://groups.google.com/d/msg/syzkaller-bugs/nEeIAsNLWL4/1GzamOmRAwAJ
"general protection fault in __wake_up_com
52 matches
Mail list logo
