On Wed, Jun 19, 2019 at 5:57 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:29f785ff Merge branch 'fixes' of git://git.kernel.org/pub/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10539ceaa0
> kernel config:
On Mon, Jun 17, 2019 at 6:00 AM Walter Wu wrote:
>
> On Fri, 2019-06-14 at 10:32 +0800, Walter Wu wrote:
> > On Fri, 2019-06-14 at 01:46 +0800, Walter Wu wrote:
> > > On Thu, 2019-06-13 at 15:27 +0300, Andrey Ryabinin wrote:
> > > >
> > > > On 6/13/19 11:13 AM, Walter Wu wrote:
> > > > > This
On Thu, Jun 13, 2019 at 2:07 PM Hillf Danton wrote:
>
>
> Hello Jason
>
> On Thu, 13 Jun 2019 17:10:39 +0800 Jason Wang wrote:
> >
> > This is basically a kfree(ubuf) after the second vhost_net_flush() in
> > vhost_net_release().
> >
> Fairly good catch.
>
> > Could you please post a formal
On Thu, Jun 13, 2019 at 2:27 PM Andrey Ryabinin wrote:
> On 6/13/19 11:13 AM, Walter Wu wrote:
> > This patch adds memory corruption identification at bug report for
> > software tag-based mode, the report show whether it is "use-after-free"
> > or "out-of-bound" error instead of "invalid-access"
On Thu, Jun 13, 2019 at 4:15 PM Hillf Danton wrote:
>
>
> Hello Dmitry
>
> On Thu, 13 Jun 2019 20:12:06 +0800 Dmitry Vyukov wrote:
> > On Thu, Jun 13, 2019 at 2:07 PM Hillf Danton wrote:
> > >
> > > Hello Jason
> > >
> >
On Tue, Jun 11, 2019 at 2:39 PM Arnd Bergmann wrote:
>
> On Tue, Jun 11, 2019 at 9:18 AM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:f4cfcfbd net: dsa: sja1105: Fix link speed not working at ..
> > git tree: net
> > console output:
,On Sun, Jun 9, 2019 at 4:56 AM Hillf Danton wrote:
>
>
> Hi
>
> On Sat, 08 Jun 2019 12:13:06 -0700 (PDT) syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:79c3ba32 Merge tag 'drm-fixes-2019-06-07-1' of git://anong..
> > git tree: upstream
> >
I should have been asked this earlier, but: what is your use-case?
Could you use CONFIG_KASAN_GENERIC instead? Why not?
CONFIG_KASAN_GENERIC already has quarantine.
On Tue, Jun 11, 2019 at 1:32 PM Dmitry Vyukov wrote:
>
> On Tue, Jun 11, 2019 at 12:44 PM Walter Wu wrote:
> >
> &g
On Tue, Jun 11, 2019 at 12:44 PM Walter Wu wrote:
>
> On Tue, 2019-06-11 at 10:47 +0200, Dmitry Vyukov wrote:
> > On Tue, Jun 11, 2019 at 9:05 AM Walter Wu wrote:
> > >
> > > On Mon, 2019-06-10 at 13:46 +0200, Dmitry Vyukov wrote:
> > > > On Mon, Jun 10,
On Tue, Jun 11, 2019 at 11:01 AM Daniel Vetter wrote:
>
> On Tue, Jun 11, 2019 at 10:51:23AM +0200, Daniel Vetter wrote:
> > On Tue, Jun 11, 2019 at 10:33:21AM +0200, Dmitry Vyukov wrote:
> > > On Tue, Jun 11, 2019 at 10:04 AM Daniel Vetter wrote:
> > > >
>
On Tue, Jun 11, 2019 at 9:05 AM Walter Wu wrote:
>
> On Mon, 2019-06-10 at 13:46 +0200, Dmitry Vyukov wrote:
> > On Mon, Jun 10, 2019 at 9:28 AM Walter Wu wrote:
> > >
> > > On Fri, 2019-06-07 at 21:18 +0800, Dmitry Vyukov wrote:
> > > > > diff
On Mon, Jun 10, 2019 at 11:27 PM Eric W. Biederman
wrote:
>
> syzbot writes:
>
> > syzbot has bisected this bug to:
> >
> > commit e9db4ef6bf4ca9894bb324c76e01b8f1a16b2650
> > Author: John Fastabend
> > Date: Sat Jun 30 13:17:47 2018 +
> >
> > bpf: sockhash fix omitted bucket lock in
On Mon, Jun 10, 2019 at 9:28 AM Walter Wu wrote:
>
> On Fri, 2019-06-07 at 21:18 +0800, Dmitry Vyukov wrote:
> > > diff --git a/include/linux/kasan.h b/include/linux/kasan.h
> > > index b40ea104dd36..be0667225b58 100644
> > > --- a/include/linux/kasan.h
option CONFIG_KASAN_SW_TAGS_IDENTIFY.
> - change QUARANTINE_FRACTION to reduce quarantine size.
> - change the qlist order in order to find the newest object in quarantine
> - reduce the number of calling kmalloc() from 2 to 1 time.
> - remove global variable to use argument to p
On Fri, Jun 7, 2019 at 10:33 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:ae3cad8f Add linux-next specific files for 20190603
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=164f802ea0
> kernel config:
On Thu, Jun 6, 2019 at 5:25 PM Kirill Tkhai wrote:
>
> On 06.06.2019 18:18, Dmitry Vyukov wrote:
> > On Thu, Jun 6, 2019 at 4:54 PM Kirill Tkhai wrote:
> >>
> >> On 06.06.2019 17:40, Dmitry Vyukov wrote:
> >>> On Thu, Jun 6, 2019 at 3:43 PM Kirill Tkhai
On Thu, Jun 6, 2019 at 4:54 PM Kirill Tkhai wrote:
>
> On 06.06.2019 17:40, Dmitry Vyukov wrote:
> > On Thu, Jun 6, 2019 at 3:43 PM Kirill Tkhai wrote:
> >>
> >> On 06.06.2019 16:13, J. Bruce Fields wrote:
> >>> On Thu, Jun 06, 2019 at 10:47:43AM
On Thu, Jun 6, 2019 at 3:52 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:156c0591 Merge tag 'linux-kselftest-5.2-rc4' of git://git...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13512d51a0
> kernel config:
On Thu, Jun 6, 2019 at 3:52 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:156c0591 Merge tag 'linux-kselftest-5.2-rc4' of git://git...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15f2095aa0
> kernel config:
On Thu, Jun 6, 2019 at 3:43 PM Kirill Tkhai wrote:
>
> On 06.06.2019 16:13, J. Bruce Fields wrote:
> > On Thu, Jun 06, 2019 at 10:47:43AM +0300, Kirill Tkhai wrote:
> >> This may be connected with that shrinker unregistering is forgotten on
> >> error path.
> >
> > I was wondering about that
On Tue, Jun 4, 2019 at 3:37 PM Xin Long wrote:
>
> On Fri, May 31, 2019 at 10:59 PM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:bec7550c Merge tag 'docs-5.2-fixes2' of git://git.lwn.net/..
> > git tree: upstream
> > console output:
.o := $(call cc-option, -fno-conserve-stack
> -fno-stack-protector)
> CFLAGS_tags.o := $(call cc-option, -fno-conserve-stack -fno-stack-protector)
>
> obj-$(CONFIG_KASAN) := common.o init.o report.o
Acked-by: Dmitry Vyukov
Is it needed in all section? Or you just followed th
On Sat, Jun 1, 2019 at 7:15 PM David Ahern wrote:
>
> On 6/1/19 12:05 AM, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:dfb569f2 net: ll_temac: Fix compile error
> > git tree: net-next
> syzbot team:
>
> Is there any way to know the history of
On Sat, Jun 1, 2019 at 7:52 PM Ganapathi Bhat wrote:
>
> Hi syzbot,
>
> >
> > syzbot found the following crash on:
> >
> As per the
> link(https://syzkaller.appspot.com/bug?extid=dc4127f950da51639216), the issue
> is fixed; Is it OK? Let us know if we need to do something?
Hi Ganapathi,
The
a On Wed, May 29, 2019 at 11:35 AM Walter Wu
wrote:
>
> > Hi Walter,
> >
> > Please describe your use case.
> > For testing context the generic KASAN works better and it does have
> > quarantine already. For prod/canary environment the quarantine may be
> > unacceptable in most cases.
> > I
On Wed, May 29, 2019 at 11:35 AM Walter Wu wrote:
>
> > Hi Walter,
> >
> > Please describe your use case.
> > For testing context the generic KASAN works better and it does have
> > quarantine already. For prod/canary environment the quarantine may be
> > unacceptable in most cases.
> > I think
On Tue, May 28, 2019 at 7:19 PM Peter Zijlstra wrote:
>
> On Tue, May 28, 2019 at 06:32:57PM +0200, Marco Elver wrote:
> > This is a pre-requisite for enabling bitops instrumentation. Some bitops
> > may safely be used with instrumentation in uaccess regions.
> >
> > For example, on x86,
and On Tue, May 28, 2019 at 9:17 AM Walter Wu
wrote:
>
> This patch adds memory corruption identification at bug report for
> software tag-based mode, the report show whether it is "use-after-free"
> or "out-of-bound" error instead of "invalid-access" error.This will make
> it easier for
On Sat, May 25, 2019 at 7:38 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:c50bbf61 Merge tag 'platform-drivers-x86-v5.2-2' of git://..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12130c9aa0
> kernel config:
On Sat, May 25, 2019 at 7:38 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:af5136f9 selftests/net: SO_TXTIME with ETF and FQ
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=13164ee4a0
> kernel config:
On Fri, May 24, 2019 at 10:08 AM Daniel Borkmann wrote:
>
> On 05/24/2019 07:28 AM, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:e6f6cd0d bpf: sockmap, fix use after free from sleep in ps..
> > git tree: bpf
> > console output:
gt; will be removed after we found what is wrong.
>
> [1]
> https://lkml.kernel.org/r/127c9c3b-f878-174f-7065-66dc50fca...@i-love.sakura.ne.jp
>
> Signed-off-by: Tetsuo Handa
> Cc: Dmitry Vyukov
> Cc: Sergey Senozhatsky
> Cc: Petr Mladek
> ---
> kernel/printk/print
On Thu, May 23, 2019 at 2:08 AM wrote:
> > From: Dmitry Vyukov
> > On Fri, Apr 26, 2019 at 11:03 PM Tim Bird wrote:
> > >
> > > I'm in the process now of planning Automated Testing Summit 2019,
> > > which is tentatively planned for Lyon, France on October
On Thu, May 16, 2019 at 2:51 AM wrote:
> > -Original Message-
> > From: Sasha Levin
> >
> > On Fri, Apr 26, 2019 at 02:02:53PM -0700, Tim Bird wrote:
> ...
> > >
> > >With regards to the Testing microconference at Plumbers, I would like
> > >to do a presentation on the current status of
On Sun, May 12, 2019 at 2:40 AM Andrea Parri
wrote:
>
> On Tue, Apr 23, 2019 at 11:22:50AM +0100, Mark Rutland wrote:
> > On Thu, Apr 11, 2019 at 10:37:51AM -0700, Dhaval Giani wrote:
> > > Hi Folks,
> > >
> > > This is a call for participation for the Linux Testing microconference
> > > at LPC
at 6:37 AM Veronika Kabatova wrote:
> >
> >
> >
> > - Original Message -
> > > From: "Dhaval Giani"
> > > To: "Sasha Levin" , "shuah"
> > > , "Kevin Hilman" ,
> > > "Tim Bird" ,
On Sat, May 18, 2019 at 10:19 PM Theodore Ts'o wrote:
>
> On Sat, May 18, 2019 at 05:21:42PM +0100, Al Viro wrote:
> > IOW, Dan's fix folded into the offending commit. And that kind of
> > pattern is not rare; I would argue that appending Dan's patch at
> > the end of queue and leaving the crap
On Sat, May 18, 2019 at 11:41 PM Al Viro wrote:
> > > What would you prefer to happen in such situations? Commit summaries
> > > modified enough to confuse CI tools into *NOT* noticing that those
> > > are versions of the same patch? Some kind of metadata telling the
> > > same tools that
.On Sat, May 18, 2019 at 6:21 PM Al Viro wrote:
>
> On Sat, May 18, 2019 at 05:00:39PM +0200, Dmitry Vyukov wrote:
> > On Fri, May 17, 2019 at 4:08 PM Dmitry Vyukov wrote:
> > >
> > > On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
> > > >
> > >
On Fri, May 17, 2019 at 4:08 PM Dmitry Vyukov wrote:
>
> On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
> >
> > On Fri, May 17, 2019 at 03:17:02AM -0700, syzbot wrote:
> > > This bug is marked as fixed by commit:
> > > vfs: namespace: error pointer dereferen
On Fri, May 17, 2019 at 8:34 PM Todd Kjos wrote:
> > On Fri, May 17, 2019 at 5:51 PM Dmitry Vyukov wrote:
> > > > > >
> > > > > > From: Dmitry Vyukov
> > > > > > Date: Fri, May 17, 2019 at 3:26 AM
> > > > > > To: G
On Fri, May 17, 2019 at 11:37 PM Andrew Morton
wrote:
>
> On Fri, 17 May 2019 19:15:07 +0200 Dmitry Vyukov wrote:
>
> > From: Dmitry Vyukov
> >
> > in_softirq() is a wrong predicate to check if we are in a softirq context.
> > It also returns true if we have BH
From: Dmitry Vyukov
in_softirq() is a wrong predicate to check if we are in a softirq context.
It also returns true if we have BH disabled, so objects are falsely
stamped with "softirq" comm. The correct predicate is in_serving_softirq().
Signed-off-by: Dmitry Vyukov
Cc: linux...@kv
On Fri, May 17, 2019 at 5:51 PM Dmitry Vyukov wrote:
> > > >
> > > > From: Dmitry Vyukov
> > > > Date: Fri, May 17, 2019 at 3:26 AM
> > > > To: Greg Kroah-Hartman, Arve Hjønnevåg, Todd Kjos, Martijn Coenen,
> > > > Joel Fernandes, C
On Fri, May 17, 2019 at 5:45 PM Dmitry Vyukov wrote:
>
> On Fri, May 17, 2019 at 5:44 PM Dmitry Vyukov wrote:
> >
> > On Fri, May 17, 2019 at 5:36 PM Todd Kjos wrote:
> > >
> > > From: Dmitry Vyukov
> > > Date: Fri, May 17, 2019 at 3:26 AM
>
On Fri, May 17, 2019 at 5:44 PM Dmitry Vyukov wrote:
>
> On Fri, May 17, 2019 at 5:36 PM Todd Kjos wrote:
> >
> > From: Dmitry Vyukov
> > Date: Fri, May 17, 2019 at 3:26 AM
> > To: Greg Kroah-Hartman, Arve Hjønnevåg, Todd Kjos, Martijn Coenen,
> > Joe
On Fri, May 17, 2019 at 5:36 PM Todd Kjos wrote:
>
> From: Dmitry Vyukov
> Date: Fri, May 17, 2019 at 3:26 AM
> To: Greg Kroah-Hartman, Arve Hjønnevåg, Todd Kjos, Martijn Coenen,
> Joel Fernandes, Christian Brauner, open list:ANDROID DRIVERS, LKML
> Cc: syzkaller
>
>
bug, please add the following tag to the commit:
> Reported-by: syzbot+f9f3f388440283da2...@syzkaller.appspotmail.com
Otherwise somebody needs to say:
#syz fix: binder: fix BUG_ON found by selinux-testsuite
> From: Dmitry Vyukov
> Date: Fri, May 17, 2019 at 3:08 AM
> To: syz
On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
>
> On Fri, May 17, 2019 at 03:17:02AM -0700, syzbot wrote:
> > This bug is marked as fixed by commit:
> > vfs: namespace: error pointer dereference in do_remount()
> > But I can't find it in any tested tree for more than 90 days.
> > Is it a correct
Hi,
I have 2 questions re drivers/android/binder.c stress testing.
1. Are there any docs on the kernel interface? Or some examples on how
to use it and reference syscall sequences to make it do something
meaningful?
I hopefully figured out struct layouts and offsets of objects thing,
but I still
On Fri, Mar 29, 2019 at 10:55 AM syzbot
wrote:
>
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger
> crash:
>
> Reported-and-tested-by:
> syzbot+f9f3f388440283da2...@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 8c2ffd91 Linux 5.1-rc2
> git tree:
From: Michael Ellerman
Date: Mon, May 13, 2019 at 1:33 PM
To: Dmitry Vyukov, Arnd Bergmann
Cc: Nick Kossifidis, Christoph Hellwig, Linus Torvalds, Andrew Morton,
linux-arch, Linux Kernel Mailing List, linuxppc-dev
> Dmitry Vyukov writes:
> > From: Arnd Bergmann
> > Date: Sat, Ma
From: Tetsuo Handa
Date: Mon, May 13, 2019 at 1:04 PM
To: Andrew Morton
Cc: Ingo Molnar, Peter Zijlstra, Paul E. McKenney, Petr Mladek, Vitaly
Kuznetsov, Liu Chuansheng, Valdis Kletnieks,
, Tetsuo Handa, Dmitry Vyukov
> syzbot's second top report is "no output from test machin
From: Arnd Bergmann
Date: Sat, May 11, 2019 at 2:51 AM
To: Dmitry Vyukov
Cc: Nick Kossifidis, Christoph Hellwig, Linus Torvalds, Andrew Morton,
linux-arch, Linux Kernel Mailing List, linuxppc-dev
> On Fri, May 10, 2019 at 6:53 AM Dmitry Vyukov wrote:
> > >
> > > I th
From: Nick Kossifidis
Date: Fri, Apr 12, 2019 at 6:08 PM
To: Arnd Bergmann
Cc: Christoph Hellwig, Linus Torvalds, Andrew Morton, linux-arch,
, Linux Kernel Mailing List
> Στις 2019-04-12 17:53, Arnd Bergmann έγραψε:
> > On Fri, Apr 12, 2019 at 4:36 PM Christoph Hellwig wrote:
> >>
> >> When
> > > > Can the KVM maintainers take a look at this? This doesn't have
> > > > anything to do
> > > > with my commit that syzbot bisected it to.
> > > >
> > > > +Dmitry, statistics lession: if a crash occurs only 1 in 10 times, as
> > > > was the
> > > > case here, then often it will happen 0
> On Tue, May 07, 2019 at 02:50:05AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:baf76f0c slip: make slhc_free() silently accept an error p..
> > git tree: upstream
> > console output:
From: Dmitry Vyukov
Date: Wed, May 8, 2019 at 1:25 PM
To: Eric Biggers
Cc: syzbot, KVM list, , David Miller, Artem
Bityutskiy, , Josh Poimboeuf, LKML,
, Andy Lutomirski, Ingo Molnar, Peter
Zijlstra, Richard Weinberger, Rik van Riel, Steven Rostedt,
syzkaller-bugs, Thomas Gleixner
> From: E
From: Julia Lawall
Date: Fri, Apr 12, 2019 at 3:21 PM
> On Fri, 12 Apr 2019, Pavel Machek wrote:
>
> > On Fri 2019-04-12 04:42:01, syzbot wrote:
> > > syzbot has bisected this bug to:
> > >
> > > commit c68729119f4d2993bec3c9cb999ad76de5aeddba
> > > Author: Julia Lawall
> > > Date: Sat Jul 15
From: Steven Rostedt
Date: Thu, May 2, 2019 at 5:10 AM
To: Eric Biggers
Cc: syzbot, Dmitry Vyukov, ,
, ,
, , ,
, ,
, , ,
, ,
,
> On Wed, 1 May 2019 19:34:27 -0700
> Eric Biggers wrote:
>
> > > Call Trace:
> > > smp_call_function_many+0x750/0x8c0 kernel/smp.c:434
&g
From: Eric Biggers
Date: Thu, May 2, 2019 at 4:34 AM
To: syzbot, Dmitry Vyukov,
Cc: , ,
, , ,
, ,
, , ,
, , ,
,
> On Wed, May 01, 2019 at 07:36:05AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:baf76f0
On Fri, Apr 26, 2019 at 8:40 PM JohnD Oracle wrote:
>
> Hi
>
>
> I am seeing a number of miss leading information in these reports , and I
> don't have an adequate understanding how KASAN
> works in order to know to debug it.
>
> For instance;
>
> Lets look at this event :
>
> kasan:
On Fri, Dec 21, 2018 at 10:37 PM Sean Christopherson
wrote:
>
> Linus pointed out that deciphering the raw #PF error code and printing
> a more human readable message are two different things, and also that
> printing the negative cases is mostly just noise[1]. For example, the
> USER bit
On Sun, Apr 28, 2019 at 8:51 PM Al Viro wrote:
>
> On Sun, Apr 28, 2019 at 11:14:06AM -0700, syzbot wrote:
> > down_read+0x49/0x90 kernel/locking/rwsem.c:26
> > __get_super.part.0+0x203/0x2e0 fs/super.c:788
> > __get_super include/linux/spinlock.h:329 [inline]
> > get_super+0x2e/0x50
On Tue, Apr 23, 2019 at 7:26 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:dc4060a5 Linux 5.1-rc5
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=146c7ab720
> kernel config:
On Mon, Apr 22, 2019 at 2:08 PM Amir Goldstein wrote:
> > > On Tue, Mar 26, 2019 at 2:10 PM syzbot
> > > wrote:
> > > >
> > > > syzbot has bisected this bug to:
> > > >
> > > > commit 01b39dcc95680b04c7af5de7f39f577e9c4865e3
> > > > Author: Amir Goldstein
> > > > Date: Fri May 11 08:15:15
On Fri, Apr 19, 2019 at 11:21 AM Amir Goldstein wrote:
>
> On Tue, Mar 26, 2019 at 2:10 PM syzbot
> wrote:
> >
> > syzbot has bisected this bug to:
> >
> > commit 01b39dcc95680b04c7af5de7f39f577e9c4865e3
> > Author: Amir Goldstein
> > Date: Fri May 11 08:15:15 2018 +
> >
> > ovl: use
On Thu, Apr 11, 2019 at 4:23 AM Al Viro wrote:
>
> On Thu, Apr 11, 2019 at 08:50:17AM +0800, Ian Kent wrote:
> > On Wed, 2019-04-10 at 14:41 +0200, Dmitry Vyukov wrote:
> > > On Wed, Apr 10, 2019 at 2:12 PM Al Viro wrote:
> > > >
> > > > On Wed, Apr
On Thu, Apr 11, 2019 at 2:50 AM Ian Kent wrote:
>
> On Wed, 2019-04-10 at 14:41 +0200, Dmitry Vyukov wrote:
> > On Wed, Apr 10, 2019 at 2:12 PM Al Viro wrote:
> > >
> > > On Wed, Apr 10, 2019 at 08:07:15PM +0800, Ian Kent wrote:
> > >
> > > &
ve that stale help text, and update it along the lines of hat
> for ARCH_HAS_FORTIFY_SOURCE, better describing when an architecture
> should select CONFIG_ARCH_HAS_KCOV.
>
> Signed-off-by: Mark Rutland
> Cc: Andrew Morton
> Cc: Dmitry Vyukov
> Cc: Kees Cook
> ---
> lib/
On Wed, Apr 10, 2019 at 2:12 PM Al Viro wrote:
>
> On Wed, Apr 10, 2019 at 08:07:15PM +0800, Ian Kent wrote:
>
> > > I'm unable to find a branch matching the line numbers.
> > >
> > > Given that, on the face of it, the scenario is impossible I'm
> > > seeking clarification on what linux-next to
On Wed, Apr 10, 2019 at 2:07 PM Ian Kent wrote:
>
> On Wed, 2019-04-10 at 19:57 +0800, Ian Kent wrote:
> > On Wed, 2019-04-10 at 13:40 +0200, Dmitry Vyukov wrote:
> > > On Wed, Apr 10, 2019 at 12:35 PM Ian Kent wrote:
> > > >
> > > > On Wed, 2
On Wed, Apr 10, 2019 at 2:02 PM Dmitry Vyukov wrote:
>
> On Wed, Apr 10, 2019 at 1:57 PM Ian Kent wrote:
> > > > > > On Tue, Apr 09, 2019 at 07:36:00AM -0700, syzbot wrote:
> > > > > > > Bisection is inconclusive: the first bad commit could be any
On Wed, Apr 10, 2019 at 1:57 PM Ian Kent wrote:
> > > > > On Tue, Apr 09, 2019 at 07:36:00AM -0700, syzbot wrote:
> > > > > > Bisection is inconclusive: the first bad commit could be any of:
> > > > >
> > > > > [snip the useless pile]
> > > > >
> > > > > > bisection log:
> > > > > >
On Wed, Apr 10, 2019 at 12:35 PM Ian Kent wrote:
>
> On Wed, 2019-04-10 at 10:27 +0200, Dmitry Vyukov wrote:
> > On Wed, Apr 10, 2019 at 2:26 AM Al Viro wrote:
> > >
> > > On Tue, Apr 09, 2019 at 07:36:00AM -0700, syzbot wrote:
> > > > Bisection is incon
On Wed, Apr 10, 2019 at 1:06 PM Thomas Gleixner wrote:
>
> Replace the indirection through struct stack_trace by using the storage
> array based interfaces.
>
> Signed-off-by: Thomas Gleixner
> Cc: Andrey Ryabinin
> Cc: Alexander Potapenko
> Cc: Dmitry Vyukov
> Cc:
On Wed, Apr 10, 2019 at 1:05 PM Thomas Gleixner wrote:
>
> No architecture terminates the stack trace with ULONG_MAX anymore. Remove
> the cruft.
>
> Signed-off-by: Thomas Gleixner
> Cc: Andrey Ryabinin
> Cc: Alexander Potapenko
> Cc: kasan-...@googlegroups.com
> Cc:
On Wed, Apr 10, 2019 at 2:26 AM Al Viro wrote:
>
> On Tue, Apr 09, 2019 at 07:36:00AM -0700, syzbot wrote:
> > Bisection is inconclusive: the first bad commit could be any of:
>
> [snip the useless pile]
>
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15e1fc2b20
> > start
On Fri, Nov 16, 2018 at 6:44 PM syzbot
wrote:
>
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit:da5322e65940 Merge tag 'selinux-pr-20181115' of git://git...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13a06f7b40
>
On Wed, May 9, 2018 at 7:03 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:036db8bd9637 Merge branch 'for-4.17-fixes' of git://git.ke..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=14d187e780
> kernel config:
On Fri, Apr 5, 2019 at 12:09 PM Florian Westphal wrote:
>
> Krzysztof Kozlowski wrote:
> > On Wed, 3 Apr 2019 at 03:14, syzbot
> > wrote:
> > >
> > > syzbot has bisected this bug to:
> > >
> > > commit 97cdcf37b57e3f204be3000b9eab9686f38b4356
> > > Author: Florian Westphal
> > > Date: Mon
On Mon, Apr 1, 2019 at 9:25 PM Paul E. McKenney wrote:
>
> On Mon, Apr 01, 2019 at 12:58:01AM -0700, syzbot wrote:
> > syzbot has bisected this bug to:
> >
> > commit 63d86a7e85f84b8ac3b2f394570965aedbb03787
> > Author: Paul E. McKenney
> > Date: Tue May 1 20:08:46 2018 +
> >
> > rcu:
n files on Linux
> > anymore.
> >
> > Signed-off-by: Johannes Thumshirn
>
> Ack-by: Nikolay Borisov
Reviewed-by: Dmitry Vyukov
Cc: sta...@vger.kernel.org # v1.0+
Do we want to extend this to other subsystems?
Should it be a default secomp filter?
> > ---
> >
On Wed, Mar 27, 2019 at 8:16 AM Amir Goldstein wrote:
>
> On Wed, Mar 27, 2019 at 5:53 AM syzbot
> wrote:
> >
> > syzbot has bisected this bug to:
> >
> > commit e950564b97fd0f541b02eb207685d0746f5ecf29
> > Author: Miklos Szeredi
> > Date: Tue Jul 24 13:01:55 2018 +
> >
> > vfs:
On Wed, Mar 27, 2019 at 12:28 AM Finn Thain wrote:
>
> On Tue, 26 Mar 2019, syzbot wrote:
>
> > syzbot has bisected this bug to:
> >
> > commit cf85d89562f39cc7ae73de54639f1915a9195b7a
> > Author: Finn Thain
> > Date: Fri May 25 07:34:36 2018 +
> >
> >m68k/mac: Enable PDMA for
Hello,
As most of you probably already noticed, syzbot started bisecting
cause commits for crashes about 2 weeks ago and sending emails like
this:
https://groups.google.com/d/msg/syzkaller-bugs/2XhfN2Kfbqs/0U3YnKsGBQAJ
The bisection results are also available on the dashboard, e.g.:
On Wed, Mar 27, 2019 at 2:28 PM Borislav Petkov wrote:
>
> On Sat, Mar 23, 2019 at 11:22:06PM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:fd1f297b Merge tag 'drm-fixes-2019-03-22' of git://anongit..
> > git tree: upstream
> > console
On Sat, Mar 23, 2019 at 2:56 PM Theodore Ts'o wrote:
>
> On Sat, Mar 23, 2019 at 08:16:36AM +0100, Dmitry Vyukov wrote:
> >
> > This is a lockdep-detected bug, but it is reproduced with very low
> > probability...
> >
> > I would expect that for lockdep i
On Sun, Mar 24, 2019 at 1:04 AM Thomas Gleixner wrote:
>
> On Sat, 23 Mar 2019, syzbot wrote:
>
> > syzbot has bisected this bug to:
> >
> > commit 80eb865768703c0f85a0603762742ae1dedf21f0
> > Author: Andrea Parri
> > Date: Tue Nov 27 11:01:10 2018 +
> >
> >sched/fair: Clean up comment
On Mon, Dec 3, 2018 at 3:53 PM Dmitry Vyukov wrote:
>
> On Sat, Dec 1, 2018 at 9:22 PM Manfred Spraul
> wrote:
> >
> > Hi Dmitry,
> >
> > On 11/30/18 6:58 PM, Dmitry Vyukov wrote:
> > > On Thu, Nov 29, 2018 at 9:13 AM, Manfred Spraul
> > > w
On Sun, Mar 24, 2019 at 7:51 PM syzbot
wrote:
>
> syzbot has bisected this bug to:
>
> commit 86f690e8bfd124c38940e7ad58875ef383003348
> Author: Greg Kroah-Hartman
> Date: Thu Mar 29 12:15:13 2018 +
>
> Merge tag 'stm-intel_th-for-greg-20180329' of
>
On Mon, Mar 25, 2019 at 9:36 AM Eric Dumazet wrote:
>
> On Mon, Mar 25, 2019 at 1:19 AM syzbot
> wrote:
> >
> > syzbot has bisected this bug to:
> >
> > commit 472c2e07eef045145bc1493cc94a01c87140780a
> > Author: Eric Dumazet
> > Date: Fri Mar 22 15:56:39 2019 +
> >
> > tcp: add one
On Sun, Mar 24, 2019 at 10:07 AM Borislav Petkov wrote:
>
> syzbot folks,
>
> please fix your bot - I got 164(!) copies of this mail. No, wait, 165.
>
> This is really annoying.
Oops. Sorry. This should be fixed by
On Fri, Mar 22, 2019 at 10:28 PM syzbot
wrote:
>
> syzbot has bisected this bug to:
>
> commit 9022ada8ab6f1f1a932a3c93815061042e6548a5
> Author: Linus Torvalds
> Date: Fri Aug 24 20:16:36 2018 +
>
> Merge branch 'for-4.19' of
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq
>
>
On Fri, Mar 22, 2019 at 1:04 PM syzbot
wrote:
>
> syzbot has bisected this bug to:
>
> commit c470abd4fde40ea6a0846a2beab642a578c0b8cd
> Author: Linus Torvalds
> Date: Sun Feb 19 22:34:00 2017 +
>
> Linux 4.10
>
> bisection log:
On Thu, Mar 21, 2019 at 7:08 AM NeilBrown wrote:
>
> On Wed, Mar 20 2019, syzbot wrote:
>
> > syzbot has bisected this bug to:
> >
> > commit dee160df820de41ff2f59a715643680822a0ab06
> > Author: NeilBrown
> > Date: Mon Nov 5 01:30:47 2018 +
> >
> > locks: use properly initialized
On Thu, Mar 14, 2019 at 11:52 AM Tetsuo Handa
wrote:
>
> On 2019/03/14 8:40, Eric Biggers wrote:
> > On Wed, Mar 13, 2019 at 07:43:38AM +0100, 'Dmitry Vyukov' via
> > syzkaller-bugs wrote:
> >>> Also, humans can sometimes find more simpler C reproduce
On Thu, Mar 14, 2019 at 11:52 AM Tetsuo Handa
wrote:
>
> On 2019/03/14 8:40, Eric Biggers wrote:
> > On Wed, Mar 13, 2019 at 07:43:38AM +0100, 'Dmitry Vyukov' via
> > syzkaller-bugs wrote:
> >>> Also, humans can sometimes find more simpler C reproduce
On Wed, Mar 13, 2019 at 7:16 PM Eric Biggers wrote:
>
> On Wed, Mar 13, 2019 at 09:24:21AM +0100, 'Dmitry Vyukov' via syzkaller-bugs
> wrote:
> > On Tue, Mar 12, 2019 at 11:50 PM Eric Biggers wrote:
> > >
> > > On Tue, Mar 12, 2019 at 09:33:44AM +0100, 'Dmitry
On Tue, Mar 19, 2019 at 1:35 PM Sergey Senozhatsky
wrote:
>
> On (03/19/19 09:10), Dmitry Vyukov wrote:
>
> [..]
>
> > In some setups we read out output with "dmesg -w" (should stream
> > output as well) in absence of a better solution. Will this b
801 - 900 of 6078 matches
Mail list logo
