Re: general protection fault in freeary

2018-12-08 Thread Dmitry Vyukov
On Sat, Dec 8, 2018 at 11:51 AM syzbot wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit:74c4a24df7ca Add linux-next specific files for 20181207 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=11a713d540 > kernel config:

Re: KMSAN: kernel-infoleak in __kvm_write_guest_page

2018-12-06 Thread Dmitry Vyukov
On Thu, Dec 6, 2018 at 10:01 AM syzbot wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit:6f0597832d81 kmsan: unpoison data passed to skb_put_xxx() .. > git tree: https://github.com/google/kmsan.git/master > console output:

Re: KASAN: use-after-free Read in blkdev_get

2018-12-05 Thread Dmitry Vyukov
On Wed, Jun 13, 2018 at 6:27 PM syzbot wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit:f5b7769eb040 Revert "debugfs: inode: debugfs_create_dir us.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=171dc83780 > kernel config:

Re: kmemleak: Early log buffer exceeded (525980) during boot

2018-12-05 Thread Dmitry Vyukov
On Wed, Nov 28, 2018 at 5:21 AM Qian Cai wrote: > On 11/10/18 11:59 AM, Catalin Marinas wrote: > > On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote: > >> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote: > >>> The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it > >>>

Re: BUG: corrupted list in freeary

2018-12-03 Thread Dmitry Vyukov
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 > > wrote: > >> Hello together, > >> > >> On 11/27/18 4:52 PM, syzbot wrote: &g

Re: BUG: corrupted list in freeary

2018-11-30 Thread Dmitry Vyukov
On Fri, Nov 30, 2018 at 5:58 PM, Dmitry Vyukov wrote: > On Thu, Nov 29, 2018 at 9:13 AM, Manfred Spraul > wrote: >> Hello together, >> >> On 11/27/18 4:52 PM, syzbot wrote: >> >> Hello, >> >> syzbot found the following crash on: >> >>

Re: BUG: corrupted list in freeary

2018-11-30 Thread Dmitry Vyukov
On Thu, Nov 29, 2018 at 9:13 AM, Manfred Spraul wrote: > Hello together, > > On 11/27/18 4:52 PM, syzbot wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit:e195ca6cb6f2 Merge branch 'for-linus' of git://git.kernel... > git tree: upstream > console output:

Re: possible deadlock in ovl_write_iter

2018-11-27 Thread Dmitry Vyukov
On Tue, Nov 27, 2018 at 4:07 PM, Amir Goldstein wrote: > On Tue, Nov 27, 2018 at 9:06 AM syzbot > wrote: >> >> syzbot has found a reproducer for the following crash on: >> >> HEAD commit:6f8b52ba442c Merge tag 'hwmon-for-v4.20-rc5' of git://git... >> git tree: upstream >> console

Re: possible deadlock in ovl_write_iter

2018-11-27 Thread Dmitry Vyukov
On Tue, Nov 27, 2018 at 8:44 AM, Amir Goldstein wrote: > On Tue, Nov 27, 2018 at 9:06 AM syzbot > wrote: >> >> syzbot has found a reproducer for the following crash on: >> >> HEAD commit:6f8b52ba442c Merge tag 'hwmon-for-v4.20-rc5' of git://git... >> git tree: upstream >> console

Re: KASAN: use-after-free Read in kvm_write_guest_offset_cached

2018-11-27 Thread Dmitry Vyukov
On Tue, Nov 27, 2018 at 7:14 AM, Wanpeng Li wrote: > > On Tue, 27 Nov 2018 at 12:51, syzbot > wrote: > > > > Hello, > > Is there beauty C codes? syzbot does not have code like: if (rand() % 2) send_C_repro(); :) > > syzbot found the following crash on: > > > > HEAD commit:442b8cea2477

Re: linux-next boot error (2)

2018-11-27 Thread Dmitry Vyukov
On Tue, Nov 27, 2018 at 11:25 AM, David Howells wrote: > Dmitry Vyukov wrote: > >> Please either use the Reported-by tag (for amended linux-next fixes >> Tested-by can make more sense and is recognized too), or tell syzbot >> separately: > > It got folded in

Re: linux-next boot error (2)

2018-11-21 Thread Dmitry Vyukov
On Tue, Sep 11, 2018 at 11:24 PM, David Howells wrote: > Stephen Rothwell wrote: > >> I will apply this fix until the proper fix arrives in the vfs tree: > > Thanks. > > David This was fixed in September, but the Reported-by tag wasn't added and nobody told syzbot that this is fixed. So the

Re: BUG: unable to handle kernel NULL pointer dereference in write_port

2018-11-21 Thread Dmitry Vyukov
On Wed, Nov 21, 2018 at 11:11 AM, Kyungtae Kim wrote: > Thank you for your reply. > But I think this kind of crash can occur in real PC as well, and I'm > just thinking of some way to stop it in the first place (if possible). > because malicious users can use this, so as to make the whole system

Re: KASAN: use-after-free Read in locks_delete_block

2018-11-20 Thread Dmitry Vyukov
On Tue, Nov 20, 2018 at 12:08 PM, Jeff Layton wrote: > On Tue, 2018-11-20 at 07:57 +0100, Dmitry Vyukov wrote: >> On Sat, Nov 17, 2018 at 3:03 PM, Bruce Fields wrote: >> > On Sat, Nov 17, 2018 at 08:33:27AM -0500, Jeff Layton wrote: >> > > Thanks for the explanati

Re: KASAN: use-after-free Read in locks_delete_block

2018-11-19 Thread Dmitry Vyukov
On Sat, Nov 17, 2018 at 3:03 PM, Bruce Fields wrote: > On Sat, Nov 17, 2018 at 08:33:27AM -0500, Jeff Layton wrote: >> Thanks for the explanation, Dmitry. I've added the tag to the patch in >> my tree. It should show up in linux-next soon. >> >> I still find it a little misleading to say that

Re: WARNING in static_key_disable_cpuslocked

2018-11-17 Thread Dmitry Vyukov
On Sat, Nov 17, 2018 at 8:25 AM, Paolo Abeni wrote: > Hi, > > On Sat, 2018-11-17 at 06:52 -0800, Ard Biesheuvel wrote: >> (+ Paolo, Dave) >> >> On Sat, 17 Nov 2018 at 01:59, syzbot >> wrote: >> > >> > Hello, >> > >> > syzbot found the following crash on: >> > >> > HEAD commit:442b8cea2477

Re: UBSAN: Undefined behaviour in mm/page_alloc.c

2018-11-16 Thread Dmitry Vyukov
On Tue, Nov 13, 2018 at 3:29 PM, Andrew Morton wrote: > On Tue, 13 Nov 2018 10:43:05 +0100 Michal Hocko wrote: > >> From: Michal Hocko >> Date: Fri, 9 Nov 2018 09:35:29 +0100 >> Subject: [PATCH] mm, page_alloc: check for max order in hot path >> >> Konstantin has noticed that kvmalloc might

Re: general protection fault in locks_remove_flock

2018-11-16 Thread Dmitry Vyukov
On Wed, Nov 7, 2018 at 7:09 AM, syzbot wrote: > syzbot has found a reproducer for the following crash on: > > HEAD commit:d881de30d29e Add linux-next specific files for 20181107 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=10a0102b40 > kernel

Re: BUG: unable to handle kernel paging request in locks_remove_file

2018-11-16 Thread Dmitry Vyukov
On Tue, Nov 6, 2018 at 9:20 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:d881de30d29e Add linux-next specific files for 20181107 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=1103882b40 > kernel config:

Re: KASAN: use-after-free Read in locks_remove_flock

2018-11-16 Thread Dmitry Vyukov
On Tue, Nov 6, 2018 at 9:03 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:d881de30d29e Add linux-next specific files for 20181107 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=16e42f5b40 > kernel config:

Re: KASAN: stack-out-of-bounds Read in locks_remove_flock

2018-11-16 Thread Dmitry Vyukov
On Tue, Nov 6, 2018 at 9:03 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:d881de30d29e Add linux-next specific files for 20181107 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=14aa485d40 > kernel config:

Re: BUG: corrupted list in locks_delete_block

2018-11-16 Thread Dmitry Vyukov
On Sun, Nov 11, 2018 at 10:18 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:442b8cea2477 Add linux-next specific files for 20181109 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=12b1262b40 > kernel config:

Re: KASAN: use-after-free Read in locks_delete_block

2018-11-16 Thread Dmitry Vyukov
On Thu, Nov 15, 2018 at 3:41 PM, NeilBrown wrote: > On Thu, Nov 15 2018, Dmitry Vyukov wrote: > >> On Wed, Nov 14, 2018 at 2:36 AM, Jeff Layton wrote: >>> On Wed, 2018-11-14 at 07:40 +1100, NeilBrown wrote: >>>> On Tue, Nov 13 2018, Jeff Layton wrote: >&g

Re: KASAN: use-after-free Read in locks_delete_block

2018-11-15 Thread Dmitry Vyukov
On Wed, Nov 14, 2018 at 2:36 AM, Jeff Layton wrote: > On Wed, 2018-11-14 at 07:40 +1100, NeilBrown wrote: >> On Tue, Nov 13 2018, Jeff Layton wrote: >> >> > On Mon, 2018-11-12 at 12:34 -0800, syzbot wrote: >> > > Hello, >> > > >> > > syzbot found the following crash on: >> > > >> > > HEAD commit:

Re: BUG: GPF in non-whitelisted uaccess (non-canonical address?)

2018-11-14 Thread Dmitry Vyukov
On Wed, Nov 14, 2018 at 4:20 AM, David Herrmann wrote: > Hey > > On Wed, Nov 14, 2018 at 1:25 AM syzbot > wrote: >> syzbot has found a reproducer for the following crash on: >> >> HEAD commit:ccda4af0f4b9 Linux 4.20-rc2 >> git tree: upstream >> console output:

Re: Re: KMSAN: uninit-value in vcs_read

2018-11-08 Thread Dmitry Vyukov
On Thu, Nov 8, 2018 at 8:48 AM, syzbot wrote: >> On Tue, May 15, 2018 at 9:26 AM, syzbot >> wrote: >>> >>> Hello, > > >>> syzbot found the following crash on: > > >>> HEAD commit:e2ab7e8abba4 kmsan: temporarily disable >>> visitAsmInstructio.. >>> git tree:

Re: KMSAN: uninit-value in vcs_read

2018-11-08 Thread Dmitry Vyukov
On Tue, May 15, 2018 at 9:26 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:e2ab7e8abba4 kmsan: temporarily disable visitAsmInstructio.. > git tree: https://github.com/google/kmsan.git/master > console output:

Re: INFO: task hung in fuse_sb_destroy

2018-11-06 Thread Dmitry Vyukov
On Mon, Nov 5, 2018 at 4:03 AM, Miklos Szeredi wrote: > On Mon, Nov 5, 2018 at 11:40 AM, Miklos Szeredi wrote: >> On Thu, Nov 1, 2018 at 12:05 PM, Dmitry Vyukov wrote: >>> On Thu, Nov 1, 2018 at 11:49 AM, syzbot >>> wrote: >>>> Hello, >

Re: [PATCH] mm, slab: remove unnecessary unlikely()

2018-11-05 Thread Dmitry Vyukov
On Mon, Nov 5, 2018 at 11:18 AM, Vlastimil Babka wrote: > +CC Dmitry > > On 11/4/18 1:50 PM, Yangtao Li wrote: >> WARN_ON() already contains an unlikely(), so it's not necessary to use >> unlikely. >> >> Signed-off-by: Yangtao Li > > Acked-by: Vlastimil Babka > > Maybe also change it back to

Re: INFO: task hung in fuse_reverse_inval_entry

2018-11-02 Thread Dmitry Vyukov
On Thu, Jul 26, 2018 at 11:12 AM, Miklos Szeredi wrote: > On Thu, Jul 26, 2018 at 10:44 AM, Miklos Szeredi wrote: >> On Wed, Jul 25, 2018 at 11:12 AM, Dmitry Vyukov wrote: >>> On Tue, Jul 24, 2018 at 5:17 PM, Miklos Szeredi wrote: > >>> Maybe more waits in fuse

Re: INFO: task hung in grab_super

2018-11-02 Thread Dmitry Vyukov
On Wed, Jul 18, 2018 at 4:17 PM, Tetsuo Handa wrote: > On 2018/07/18 23:11, Dmitry Vyukov wrote: >> On Wed, Jul 18, 2018 at 3:35 PM, Tetsuo Handa >> wrote: >>>>>> This seems to be related to 9p. After rerunning the log I got: >>>>>> >

Re: WARNING: refcount bug in kobject_put

2018-11-02 Thread Dmitry Vyukov
On Fri, Nov 2, 2018 at 4:31 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:e468f5c06b5e Merge tag 'compiler-attributes-for-linus-4.20.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=17ad34b940 > kernel config:

Re: INFO: task hung in fuse_sb_destroy

2018-11-01 Thread Dmitry Vyukov
On Thu, Nov 1, 2018 at 11:49 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:59fc453b21f7 Merge branch 'akpm' (patches from Andrew) > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=15fb244740 > kernel config:

Re: WARNING in get_unlocked_entry

2018-10-31 Thread Dmitry Vyukov
On Wed, Oct 31, 2018 at 8:18 PM, Matthew Wilcox wrote: > On Wed, Oct 31, 2018 at 10:46:19AM +0100, Dmitry Vyukov wrote: >> On Wed, Oct 31, 2018 at 4:18 AM, Matthew Wilcox wrote: >> > On Tue, Oct 30, 2018 at 08:00:03AM -0700, syzbot wrote: >> >> sy

Re: WARNING in get_unlocked_entry

2018-10-31 Thread Dmitry Vyukov
On Wed, Oct 31, 2018 at 4:18 AM, Matthew Wilcox wrote: > On Tue, Oct 30, 2018 at 08:00:03AM -0700, syzbot wrote: >> syzbot found the following crash on: >> >> HEAD commit:4b42745211af Merge tag 'armsoc-soc' of git://git.kernel.or.. >> git tree: upstream >> console output:

Re: WARNING in get_unlocked_entry

2018-10-31 Thread Dmitry Vyukov
On Wed, Oct 31, 2018 at 4:18 AM, Matthew Wilcox wrote: > On Tue, Oct 30, 2018 at 08:00:03AM -0700, syzbot wrote: >> syzbot found the following crash on: >> >> HEAD commit:4b42745211af Merge tag 'armsoc-soc' of git://git.kernel.or.. >> git tree: upstream >> console output:

Re: WARNING in ext4_invalidatepage

2018-10-30 Thread Dmitry Vyukov
On Tue, Oct 16, 2018 at 5:53 PM, Theodore Y. Ts'o wrote: >> > The patch I referenced in my previous e-mail protects against >> > additional scenarios where someone might be trying to punch a whole >> > into a file that is being swapped into the bootloader ioctl. This >> > particular ioctl isn't

Re: WARNING in ext4_invalidatepage

2018-10-30 Thread Dmitry Vyukov
On Tue, Oct 16, 2018 at 5:53 PM, Theodore Y. Ts'o wrote: > On Tue, Oct 16, 2018 at 04:02:07PM +0200, Dmitry Vyukov wrote: >> I am not sure how exactly this should be classified. To significant >> degree these "$FOO" discriminations are informational and only really

Re: INFO: rcu detected stall in do_idle

2018-10-27 Thread Dmitry Vyukov
On Wed, Oct 24, 2018 at 1:03 PM, Juri Lelli wrote: > > On 19/10/18 22:50, luca abeni wrote: > > On Fri, 19 Oct 2018 13:39:42 +0200 > > Peter Zijlstra wrote: > > > > > On Thu, Oct 18, 2018 at 01:08:11PM +0200, luca abeni wrote: > > > > Ok, I see the issue now: the problem is that the "while > > >

Re: WARNING in ext4_invalidatepage

2018-10-16 Thread Dmitry Vyukov
On Mon, Oct 15, 2018 at 8:08 PM, Theodore Y. Ts'o wrote: > On Mon, Oct 15, 2018 at 03:22:42PM +0200, Dmitry Vyukov wrote: >> Now that you mention EXT4_IOC_SWAP_BOOT, I think I looked at the wrong >> program, there is a subsequent one that does ioctl(0x6611) where >&

Re: INFO: task hung in fanotify_handle_event

2018-10-15 Thread Dmitry Vyukov
On Mon, Oct 15, 2018 at 2:45 PM, Jan Kara wrote: > Hi Dmirty! > > On Mon 15-10-18 14:29:14, Dmitry Vyukov wrote: >> On Mon, Oct 15, 2018 at 2:15 PM, Jan Kara wrote: >> > Hello, >> > >> > On Mon 15-10-18 04:32:02, syzbot wrote: >> >> syzbot

Re: WARNING in ext4_invalidatepage

2018-10-15 Thread Dmitry Vyukov
On Tue, Oct 9, 2018 at 3:34 AM, Theodore Y. Ts'o wrote: > On Mon, Oct 08, 2018 at 06:29:54PM +0200, Dmitry Vyukov wrote: >> >> The program that triggered it did the following: >> >> 05:23:28 executing program 5: >> r0 = creat(&(0x7f0001c0)='./file0\x00',

Re: INFO: task hung in fanotify_handle_event

2018-10-15 Thread Dmitry Vyukov
On Mon, Oct 15, 2018 at 2:15 PM, Jan Kara wrote: > Hello, > > On Mon 15-10-18 04:32:02, syzbot wrote: >> syzbot found the following crash on: >> >> HEAD commit:90ad18418c2d Merge git://git.kernel.org/pub/scm/linux/kern.. >> git tree: upstream >> console output:

Re: WARNING: refcount bug in kvm_vm_ioctl

2018-10-11 Thread Dmitry Vyukov
On Thu, Oct 11, 2018 at 8:23 PM, Dmitry Vyukov wrote: > On Thu, Oct 11, 2018 at 4:17 PM, Paolo Bonzini wrote: >> On 10/10/2018 09:58, syzbot wrote: >>> do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316 >>> invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:993 >>

Re: WARNING: refcount bug in kvm_vm_ioctl

2018-10-11 Thread Dmitry Vyukov
On Thu, Oct 11, 2018 at 4:17 PM, Paolo Bonzini wrote: > On 10/10/2018 09:58, syzbot wrote: >> do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316 >> invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:993 >> RIP: 0010:refcount_inc_checked+0x5d/0x70 lib/refcount.c:153 >> kvm_get_kvm

Re: kernel BUG at arch/x86/kvm/x86.c:LINE! (2)

2018-10-11 Thread Dmitry Vyukov
On Thu, Oct 11, 2018 at 4:32 PM, Paolo Bonzini wrote: > On 11/10/2018 04:57, Du Changbin wrote: >> I think the issue is that using vmx instructions after vmx off. The >> scenario is: >> 1. kernel is rebooting and vmx is turned off by notification handler >> kvm_reboot(), >>and 'kvm_rebooting'

Re: BUG: corrupted list in p9_read_work

2018-10-11 Thread Dmitry Vyukov
On Thu, Oct 11, 2018 at 3:27 PM, Dmitry Vyukov wrote: > On Thu, Oct 11, 2018 at 3:10 PM, Dominique Martinet > wrote: >> Dmitry Vyukov wrote on Thu, Oct 11, 2018: >>> > That's still the tricky part, I'm afraid... Making a separate server >>> > would have been e

Re: BUG: corrupted list in p9_read_work

2018-10-11 Thread Dmitry Vyukov
On Thu, Oct 11, 2018 at 3:10 PM, Dominique Martinet wrote: > Dmitry Vyukov wrote on Thu, Oct 11, 2018: >> > That's still the tricky part, I'm afraid... Making a separate server >> > would have been easy because I could have reused some of my junk for the >> > actual

Re: BUG: corrupted list in p9_read_work

2018-10-11 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 5:58 PM, Dominique Martinet wrote: > Dmitry Vyukov wrote on Wed, Oct 10, 2018: >> > The problem is that you can't just give the client a file like trans fd; >> > you'd need to open an ""rdma socket"" (simplifying wording a bit),

Re: net/tipc: recursive locking in tipc_link_reset

2018-10-11 Thread Dmitry Vyukov
On Thu, Oct 11, 2018 at 2:03 PM, Ying Xue wrote: >>> Hi, >>> >>> I am getting the following error while booting the latest kernel on >>> bb2d8f2f61047cbde08b78ec03e4ebdb01ee5434 (Oct 10). Config is attached. >>> >>> Since this happens during boot, this makes LOCKDEP completely >>> unusable, does

Re: [Announce] LPC 2018: Testing and Fuzzing Microconference

2018-10-11 Thread Dmitry Vyukov
On Thu, Oct 11, 2018 at 10:54 AM, Dmitry Vyukov wrote: >>> On Mon, 8 Oct 2018 19:02:51 +0200 >>> Dmitry Vyukov wrote: >>> >>> > On Wed, Sep 19, 2018 at 7:13 PM, Dhaval Giani >>> > wrote: >>> > > Hi folks, >>> &g

Re: [Announce] LPC 2018: Testing and Fuzzing Microconference

2018-10-11 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 5:47 PM, Dhaval Giani wrote: > On Mon, Oct 8, 2018 at 11:23 AM Steven Rostedt wrote: >> >> On Mon, 8 Oct 2018 19:02:51 +0200 >> Dmitry Vyukov wrote: >> >> > On Wed, Sep 19, 2018 at 7:13 PM, Dhaval Giani >> > wrote: >>

Re: [PATCH] mm/kasan: make quarantine_lock a raw_spinlock_t

2018-10-11 Thread Dmitry Vyukov
or > [bigeasy: slightly altered the commit message] > Signed-off-by: Sebastian Andrzej Siewior Acked-by: Dmitry Vyukov > --- > On 2018-10-10 11:57:41 [+0200], Dmitry Vyukov wrote: >> Yes. Clark's patch looks good to me. Probably would be useful to add a >> comment as to

Re: net/tipc: recursive locking in tipc_link_reset

2018-10-11 Thread Dmitry Vyukov
On Thu, Oct 11, 2018 at 9:55 AM, Dmitry Vyukov wrote: > Hi, > > I am getting the following error while booting the latest kernel on > bb2d8f2f61047cbde08b78ec03e4ebdb01ee5434 (Oct 10). Config is attached. > > Since this happens during boot, this makes LOCKDEP completely > unu

Re: KASAN: slab-out-of-bounds Read in vhci_hub_control

2018-10-11 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 10:26 PM, Shuah Khan wrote: > On 10/10/2018 01:42 PM, Dmitry Vyukov wrote: >> On Tue, Oct 2, 2018 at 6:04 PM, Shuah Khan wrote: >>> On 09/04/2018 12:52 PM, syzbot wrote: >>>> Hello, >>>> >>>> syzbot found the foll

Re: KASAN: use-after-free Read in sctp_id2assoc

2018-10-10 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 8:13 PM, Marcelo Ricardo Leitner wrote: > On Wed, Oct 10, 2018 at 05:28:12PM +0200, Dmitry Vyukov wrote: >> On Fri, Oct 5, 2018 at 4:58 PM, Marcelo Ricardo Leitner >> wrote: >> > On Thu, Oct 04, 2018 at 01:48:03AM -0700, syzbot wrote: >> >

Re: kernel BUG at arch/x86/mm/physaddr.c:LINE!

2018-10-10 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 5:22 PM, Thomas Gleixner wrote: > On Wed, 10 Oct 2018, syzbot wrote: > > Cc+: Miklos It seems reasonable to ignore arch/.*/mm/physaddr.c as suspected guilty file in future -- we already ignore everything related to kmalloc/kfree and this is called from kfree. I've made

Re: INFO: rcu detected stall in shmem_fault

2018-10-10 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 3:10 PM, Tetsuo Handa wrote: >>> Just flooding out of memory messages can trigger RCU stall problems. >>> For example, a severe skbuff_head_cache or kmalloc-512 leak bug is >>> causing >> >> [...] >> >> Quite some of them, indeed! I guess we

Re: WARNING in __put_task_struct (2)

2018-10-10 Thread Dmitry Vyukov
On Tue, Oct 9, 2018 at 1:30 PM, Leon Romanovsky wrote: > On Mon, Oct 08, 2018 at 01:45:13PM -0600, Jason Gunthorpe wrote: >> On Mon, Oct 08, 2018 at 06:15:22PM +0200, Dmitry Vyukov wrote: >> > On Mon, Oct 8, 2018 at 6:12 PM, syzbot >> > wrote: >> >

Re: WARNING: ODEBUG bug in free_task

2018-10-10 Thread Dmitry Vyukov
On Tue, Oct 9, 2018 at 7:14 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:ae16eea39a86 Add linux-next specific files for 20181008 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=16a493b940 > kernel config:

Re: INFO: rcu detected stall in shmem_fault

2018-10-10 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 2:29 PM, Dmitry Vyukov wrote: > On Wed, Oct 10, 2018 at 2:25 PM, Michal Hocko wrote: >> On Wed 10-10-18 20:48:33, Sergey Senozhatsky wrote: >>> On (10/10/18 13:35), Michal Hocko wrote: >>> > > Just flooding out of memory messag

Re: INFO: rcu detected stall in shmem_fault

2018-10-10 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 2:25 PM, Michal Hocko wrote: > On Wed 10-10-18 20:48:33, Sergey Senozhatsky wrote: >> On (10/10/18 13:35), Michal Hocko wrote: >> > > Just flooding out of memory messages can trigger RCU stall problems. >> > > For example, a severe skbuff_head_cache or kmalloc-512 leak bug

Re: [PATCH] kasan: convert kasan/quarantine_lock to raw_spinlock

2018-10-10 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 11:53 AM, Sebastian Andrzej Siewior wrote: > On 2018-10-10 11:45:32 [+0200], Dmitry Vyukov wrote: >> > Should I repost Clark's patch? >> >> >> I am much more comfortable with just changing the type of the lock. > > Yes, that is what

Re: [PATCH] kasan: convert kasan/quarantine_lock to raw_spinlock

2018-10-10 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 11:29 AM, Sebastian Andrzej Siewior wrote: > On 2018-10-10 10:25:42 [+0200], Dmitry Vyukov wrote: >> > That loop should behave like your on_each_cpu() except it does not >> > involve the remote CPU. >> >> >> The pr

Re: INFO: rcu detected stall in shmem_fault

2018-10-10 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 11:13 AM, Michal Hocko wrote: > On Wed 10-10-18 09:55:57, Dmitry Vyukov wrote: >> On Wed, Oct 10, 2018 at 6:11 AM, 'David Rientjes' via syzkaller-bugs >> wrote: >> > On Wed, 10 Oct 2018, Tetsuo Handa wrote: >> > >> >> syzbo

Re: [PATCH] kasan: convert kasan/quarantine_lock to raw_spinlock

2018-10-10 Thread Dmitry Vyukov
On Tue, Oct 9, 2018 at 4:27 PM, Sebastian Andrzej Siewior wrote: > On 2018-10-08 11:15:57 [+0200], Dmitry Vyukov wrote: >> Hi Sebastian, > Hi Dmitry, > >> This seems to beak quarantine_remove_cache( ) in the sense that some >> object from the cache may

Re: INFO: rcu detected stall in shmem_fault

2018-10-10 Thread Dmitry Vyukov
On Wed, Oct 10, 2018 at 6:11 AM, 'David Rientjes' via syzkaller-bugs wrote: > On Wed, 10 Oct 2018, Tetsuo Handa wrote: > >> syzbot is hitting RCU stall due to memcg-OOM event. >> https://syzkaller.appspot.com/bug?id=4ae3fff7fcf4c33a47c1192d2d62d2e03efffa64 >> >> What should we do if memcg-OOM

Re: [Announce] LPC 2018: Testing and Fuzzing Microconference

2018-10-08 Thread Dmitry Vyukov
On Wed, Sep 19, 2018 at 7:13 PM, Dhaval Giani wrote: > Hi folks, > > Sasha and I are pleased to announce the Testing and Fuzzing track at > LPC [ 1 ]. We are planning to continue the discussions from last > year's microconference [2]. Many discussions from the Automated > Testing Summit [3] will

Re: WARNING in ext4_invalidatepage

2018-10-08 Thread Dmitry Vyukov
On Mon, Oct 8, 2018 at 6:18 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:c1d84a1b42ef Merge git://git.kernel.org/pub/scm/linux/kern.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=161588d640 > kernel config:

Re: WARNING in __put_task_struct (2)

2018-10-08 Thread Dmitry Vyukov
On Mon, Oct 8, 2018 at 6:12 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:ae16eea39a86 Add linux-next specific files for 20181008 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=12e7c6a140 > kernel config:

Re: [PATCH] kasan: convert kasan/quarantine_lock to raw_spinlock

2018-10-08 Thread Dmitry Vyukov
On Fri, Oct 5, 2018 at 6:33 PM, Sebastian Andrzej Siewior wrote: > On 2018-10-05 18:30:18 [+0200], To Clark Williams wrote: >> This is the minimum to get this working on RT splat free. There is one >> memory deallocation with irqs off which should work on RT in its current >> way. >> Once this

Re: BUG: workqueue lockup (4)

2018-10-07 Thread Dmitry Vyukov
On Sun, Oct 7, 2018 at 2:15 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:c1d84a1b42ef Merge git://git.kernel.org/pub/scm/linux/kern.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=14c5f49140 > kernel config:

Re: KASAN: use-after-scope in ext4_group_desc_csum

2018-10-05 Thread Dmitry Vyukov
On Fri, Oct 5, 2018 at 3:05 PM, Jan Glauber wrote: > On Fri, Oct 05, 2018 at 01:13:52PM +0200, Dmitry Vyukov wrote: >> On Fri, Oct 5, 2018 at 12:16 PM, Jan Glauber wrote: >> > Hi, >> > >> > I'm getting below warning when I enable CONFIG_KASAN_EXTRA

Re: KASAN: use-after-scope in ext4_group_desc_csum

2018-10-05 Thread Dmitry Vyukov
On Fri, Oct 5, 2018 at 12:16 PM, Jan Glauber wrote: > Hi, > > I'm getting below warning when I enable CONFIG_KASAN_EXTRA=y on a arm64 > ThunderX2 system. > As far as I can tell this is present since KASAN_EXTRA was introduced (4.16). > > [ 64.547333] >

Re: general protection fault in __aa_lookupn_ns

2018-09-28 Thread Dmitry Vyukov
On Fri, Sep 28, 2018 at 10:40 AM, Dmitry Vyukov wrote: > On Wed, Sep 26, 2018 at 9:52 AM, syzbot > wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:dad486875956 Add linux-next specific files for 20180924 >> git tree:

Re: KASAN: slab-out-of-bounds Read in string (2)

2018-09-28 Thread Dmitry Vyukov
On Fri, Sep 28, 2018 at 4:45 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:c127e59bee3e Merge tag 'for_v4.19-rc6' of git://git.kernel.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=13b2f32a40 > kernel config:

Re: general protection fault in __aa_lookupn_ns

2018-09-28 Thread Dmitry Vyukov
On Wed, Sep 26, 2018 at 9:52 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:dad486875956 Add linux-next specific files for 20180924 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=15da1fd140 > kernel config:

Re: BUG: MAX_LOCKDEP_CHAINS too low!

2018-09-28 Thread Dmitry Vyukov
On Fri, Sep 28, 2018 at 9:00 AM, Peter Zijlstra wrote: >> > Hello, >> > >> > syzbot found the following crash on: >> > >> > HEAD commit:c307aaf3eb47 Merge tag 'iommu-fixes-v4.19-rc5' of >> > git://gi.. >> > git tree: upstream >> > console output:

Re: BUG: MAX_LOCKDEP_CHAINS too low!

2018-09-28 Thread Dmitry Vyukov
On Fri, Sep 28, 2018 at 7:51 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:c307aaf3eb47 Merge tag 'iommu-fixes-v4.19-rc5' of git://gi.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=13810df140 > kernel config:

Re: KASAN: use-after-free Read in tcf_block_find

2018-09-27 Thread Dmitry Vyukov
On Thu, Sep 27, 2018 at 7:50 PM, Cong Wang wrote: > On Thu, Sep 27, 2018 at 1:11 AM Dmitry Vyukov wrote: >> >> Would a stack trace for call_rcu be helpful here? I have this idea for >> a long time, but never get around to implementing it: >> https://bugzilla.kernel

Re: [PATCH] mm: don't warn about large allocations for slab

2018-09-27 Thread Dmitry Vyukov
On Thu, Sep 27, 2018 at 5:51 PM, Christopher Lameter wrote: > On Thu, 27 Sep 2018, Dmitry Vyukov wrote: > >> From: Dmitry Vyukov >> >> This warning does not seem to be useful. Most of the time it fires when >> allocation size depends on syscall argume

[PATCH v2] mm: don't warn about large allocations for slab

2018-09-27 Thread Dmitry Vyukov
From: Dmitry Vyukov Slub does not call kmalloc_slab() for sizes > KMALLOC_MAX_CACHE_SIZE, instead it falls back to kmalloc_large(). For slab KMALLOC_MAX_CACHE_SIZE == KMALLOC_MAX_SIZE and it calls kmalloc_slab() for all allocations relying on NULL return value for over-sized allocati

Re: WARNING: kmalloc bug in input_mt_init_slots

2018-09-27 Thread Dmitry Vyukov
On Thu, Sep 27, 2018 at 5:22 PM, Christopher Lameter wrote: > On Thu, 27 Sep 2018, Dmitry Vyukov wrote: > >> On Thu, Sep 27, 2018 at 4:16 PM, Christopher Lameter wrote: >> > On Thu, 27 Sep 2018, Dmitry Vyukov wrote: >> > >> >> On Tue, Sep 25, 2018 at

Re: WARNING: kmalloc bug in input_mt_init_slots

2018-09-27 Thread Dmitry Vyukov
On Thu, Sep 27, 2018 at 4:16 PM, Christopher Lameter wrote: > On Thu, 27 Sep 2018, Dmitry Vyukov wrote: > >> On Tue, Sep 25, 2018 at 4:04 PM, Christopher Lameter wrote: >> > On Tue, 25 Sep 2018, Dmitry Vyukov wrote: >> > >> >> Assuming that the size

Re: KASAN: use-after-free Read in tcf_block_find

2018-09-27 Thread Dmitry Vyukov
On Thu, Sep 27, 2018 at 3:24 PM, Eric Dumazet wrote: > On 09/27/2018 06:02 AM, Dmitry Vyukov wrote: > >> I am not suggesting to commit this. This is just a hack for debugging. >> It in fact lead to some warnings, but still allowed me to reproduce >> the bug reliably.

Re: WARNING: kmalloc bug in input_mt_init_slots

2018-09-27 Thread Dmitry Vyukov
On Tue, Sep 25, 2018 at 4:04 PM, Christopher Lameter wrote: > On Tue, 25 Sep 2018, Dmitry Vyukov wrote: > >> Assuming that the size is large enough to fail in all allocators, is >> this warning still useful? How? Should we remove it? > > Remove it. It does not make sense

[PATCH] mm: don't warn about large allocations for slab

2018-09-27 Thread Dmitry Vyukov
From: Dmitry Vyukov This warning does not seem to be useful. Most of the time it fires when allocation size depends on syscall arguments. We could add __GFP_NOWARN to these allocation sites, but having a warning only to suppress it does not make lots of sense. Moreover, this warnings never fires

Re: KASAN: use-after-free Read in tcf_block_find

2018-09-27 Thread Dmitry Vyukov
On Thu, Sep 27, 2018 at 3:00 PM, Eric Dumazet wrote: > > > On 09/27/2018 01:10 AM, Dmitry Vyukov wrote: > >> >> Would a stack trace for call_rcu be helpful here? I have this idea for >> a long time, but never get around to implementing it: >> https://bugzil

Re: KMSAN: uninit-value in memcmp (2)

2018-09-27 Thread Dmitry Vyukov
uninit-value in <...>" > report. No, it did not do any damage. This is in fact already re-reported as "KMSAN: uninit-value in __dev_mc_add": https://syzkaller.appspot.com/bug?id=0766d38c656abeace60621896d705743aeefed51 > - Original Message - >> From: "Dmitry Vyukov&

Re: bpfilter breaks IPT_SO_GET_INFO

2018-09-25 Thread Dmitry Vyukov
On Wed, Sep 19, 2018 at 10:29 AM, Dmitry Vyukov wrote: > On Wed, Sep 19, 2018 at 9:18 AM, Michal Kubecek wrote: >> On Mon, Sep 17, 2018 at 03:36:21PM +0200, Dmitry Vyukov wrote: >>> Hi, >>> >>> I am having some problem with upstream kernel

Re: WARNING in request_end

2018-09-25 Thread Dmitry Vyukov
On Tue, Sep 25, 2018 at 11:18 AM, Kirill Tkhai wrote: > On 24.09.2018 17:44, Miklos Szeredi wrote: >> On Mon, Sep 24, 2018 at 2:29 PM, syzbot >> wrote: >>> Hello, >>> >>> syzbot found the following crash on: >>> >>> HEAD commit:6bf4ca7fbc85 Linux 4.19-rc5 >>> git tree: upstream >>>

Re: WARNING: kmalloc bug in input_mt_init_slots

2018-09-25 Thread Dmitry Vyukov
On Mon, Sep 24, 2018 at 8:41 PM, Dmitry Torokhov wrote: > On Mon, Sep 24, 2018 at 03:55:04PM +, Christopher Lameter wrote: >> On Mon, 24 Sep 2018, Dmitry Vyukov wrote: >> >> > On Mon, Sep 24, 2018 at 5:08 PM, Christopher Lameter >> > wrote: >> >

Re: WARNING: kmalloc bug in input_mt_init_slots

2018-09-24 Thread Dmitry Vyukov
On Mon, Sep 24, 2018 at 5:08 PM, Christopher Lameter wrote: > On Sun, 23 Sep 2018, Dmitry Vyukov wrote: > >> What was the motivation behind that WARNING about large allocations in >> kmalloc? Why do we want to know about them? Is the general policy that >> kmalloc call

Re: [Announce] LPC 2018: Testing and Fuzzing Microconference

2018-09-24 Thread Dmitry Vyukov
On Sat, Sep 22, 2018 at 2:52 PM, Matthew Wilcox wrote: > On Wed, Sep 19, 2018 at 10:13:15AM -0700, Dhaval Giani wrote: >> Sasha and I are pleased to announce the Testing and Fuzzing track at >> LPC [ 1 ]. We are planning to continue the discussions from last >> year's microconference [2]. Many

Re: INFO: task hung in fsnotify_connector_destroy_workfn (2)

2018-09-24 Thread Dmitry Vyukov
On Mon, Sep 24, 2018 at 3:19 PM, Jiri Kosina wrote: > On Sun, 16 Sep 2018, Amir Goldstein wrote: > >> > > syzbot found the following crash on: >> > > >> > > HEAD commit:11da3a7f84f1 Linux 4.19-rc3 >> > > git tree: upstream >> > > console output:

Re: [PATCH] framewarn: expand KASAN_EXTRA exception to KASAN

2018-09-24 Thread Dmitry Vyukov
On Sat, Sep 22, 2018 at 4:56 PM, Arnd Bergmann wrote: > On Fri, Sep 21, 2018 at 2:45 AM Dmitry Vyukov wrote: >> >> On Fri, Sep 21, 2018 at 11:25 AM, Andrey Ryabinin >> wrote: >> > On 09/21/2018 04:50 AM, Andy Lutomirski wrote: >> >> This patch seems re

Re: WARNING: kmalloc bug in input_mt_init_slots

2018-09-23 Thread Dmitry Vyukov
On Fri, Sep 21, 2018 at 7:52 PM, Dmitry Torokhov wrote: > On Fri, Sep 21, 2018 at 10:24 AM syzbot > wrote: >> >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:234b69e3e089 ocfs2: fix ocfs2 read block panic >> git tree: upstream >> console output:

Re: [PATCH] framewarn: expand KASAN_EXTRA exception to KASAN

2018-09-21 Thread Dmitry Vyukov
On Fri, Sep 21, 2018 at 11:25 AM, Andrey Ryabinin wrote: > On 09/21/2018 04:50 AM, Andy Lutomirski wrote: >> This patch seems reasonable, but you emailed the wrong people :) >> >> On Thu, Sep 20, 2018 at 5:15 PM Jason A. Donenfeld wrote: >>> >>> It turns out that KASAN in general will bloat

Re: [PATCH] framewarn: expand KASAN_EXTRA exception to KASAN

2018-09-21 Thread Dmitry Vyukov
4 if (!64BIT && !PARISC) Looks fine to me. KASAN always increases stack size too for exactly that reason, so it's reasonable to allow larger frames rather than try to massage code every here and there to fit into the normal frame size. Acked-by: Dmitry Vyukov Thanks

Re: possible deadlock in __do_page_fault

2018-09-21 Thread Dmitry Vyukov
On Fri, Sep 21, 2018 at 1:33 AM, Joel Fernandes wrote: > On Thu, Sep 20, 2018 at 5:12 PM Todd Kjos wrote: >> >> +Joel Fernandes >> >> On Thu, Sep 20, 2018 at 2:11 PM Andrew Morton >> wrote: >> > >> > >> > Thanks. Let's cc the ashmem folks. >> > > > This should be fixed by

  1   2   3   4   5   6   7   8   9   10   >