Re: mainline boot is broken: KASAN: use-after-free in blk_flush_complete_seq

On Sat, Jun 9, 2018 at 2:33 PM, Jens Axboe wrote: > On 6/9/18 3:34 AM, Dmitry Vyukov wrote: >> Hi, >> >> Boot of mainline kernel is currently broken. >> On commit 7d3bf613e99abbd96ac7b90ee3694a246c975021. >> Config: >> https://gist.githubusercontent.com/d

Re: INFO: task hung in blk_queue_enter

On Wed, May 16, 2018 at 4:56 PM, Bart Van Assche wrote: > On Wed, 2018-05-16 at 22:05 +0900, Tetsuo Handa wrote: >> One ore more threads are waiting for q->mq_freeze_depth to become 0. But the >> thread who incremented q->mq_freeze_depth at blk_freeze_queue_start(q) from

Re: [PATCH] loop: add recursion validation to LOOP_CHANGE_FD

On Wed, May 9, 2018 at 4:02 PM, Theodore Y. Ts'o <ty...@mit.edu> wrote: > On Wed, May 09, 2018 at 10:49:54AM +0200, Dmitry Vyukov wrote: >> Hi Ted, >> >> Did you follow all instructions (commit, config, compiler, etc)? >> syzbot does not have any special magi

Re: inconsistent lock state in fs_reclaim_acquire (2)

On Thu, May 10, 2018 at 7:57 AM, 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:

Re: [PATCH] loop: add recursion validation to LOOP_CHANGE_FD

On Tue, May 8, 2018 at 5:56 AM, Theodore Y. Ts'o wrote: > On Tue, May 08, 2018 at 09:28:17AM +0900, Tetsuo Handa wrote: >> The thread I mean is: >> >> general protection fault in lo_ioctl (2) >> >> https://syzkaller.appspot.com/bug?id=f3cfe26e785d85f9ee259f385515291d21bd80a3

Re: general protection fault in lo_ioctl (2)

On Wed, May 2, 2018 at 9:33 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:fff75eb2a08c Merge tag 'errseq-v4.17' of > git://git.kernel.o... > git tree: upstream > console output:

Re: [PATCH] loop: fix LOOP_GET_STATUS lock imbalance

On Sat, Apr 7, 2018 at 9:27 AM, Tetsuo Handa wrote: > Omar Sandoval wrote: >> From: Omar Sandoval >> >> Commit 2d1d4c1e591f made loop_get_status() drop lo_ctx_mutex before >> returning, but the loop_get_status_old(), loop_get_status64(), and >>

Re: WARNING: lock held when returning to user space!

On Fri, Apr 6, 2018 at 4:27 PM, Jens Axboe wrote: > On 4/6/18 7:02 AM, syzbot wrote: >> Hello, >> >> syzbot hit the following crash on upstream commit >> 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +) >> Merge tag 'armsoc-drivers' of >>

Re: INFO: task hung in blk_freeze_queue

On Wed, Feb 7, 2018 at 8:46 AM, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > e237f98a9c134c3d600353f21e07db915516875b (Mon Feb 5 21:35:56 2018 +) > Merge tag 'xfs-4.16-merge-5' of >

Re: WARNING in kmalloc_slab (3)

On Tue, Dec 12, 2017 at 10:22 PM, Eric Biggers <ebigge...@gmail.com> wrote: > On Mon, Dec 04, 2017 at 12:26:32PM +0300, Dan Carpenter wrote: >> On Mon, Dec 04, 2017 at 09:18:05AM +0100, Dmitry Vyukov wrote: >> > On Mon, Dec 4, 2017 at 9:14 AM, Dan Carpenter <dan.carpen

Re: scsi: memory leak in sg_start_req

On Thu, Jan 11, 2018 at 7:04 AM, Douglas Gilbert <dgilb...@interlog.com> wrote: > On 2018-01-09 11:05 AM, Dmitry Vyukov wrote: >> >> Hello, >> >> syzkaller has found the following memory leak: >> >> unreferenced object 0x88004c19 (size 8328):

scsi: memory leak in sg_start_req

Hello, syzkaller has found the following memory leak: unreferenced object 0x88004c19 (size 8328): comm "syz-executor", pid 4627, jiffies 4294749150 (age 45.507s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 22 01 00

Re: WARNING in kmalloc_slab (3)

On Mon, Dec 4, 2017 at 10:26 AM, Dan Carpenter <dan.carpen...@oracle.com> wrote: > On Mon, Dec 04, 2017 at 09:18:05AM +0100, Dmitry Vyukov wrote: >> On Mon, Dec 4, 2017 at 9:14 AM, Dan Carpenter <dan.carpen...@oracle.com> >> wrote: >> > On Sun, Dec 03, 2017 at

Re: WARNING in kmalloc_slab (3)

On Mon, Dec 4, 2017 at 9:14 AM, Dan Carpenter wrote: > On Sun, Dec 03, 2017 at 12:16:08PM -0800, Eric Biggers wrote: >> Looks like BLKTRACESETUP doesn't limit the '.buf_nr' parameter, allowing >> anyone >> who can open a block device to cause an extremely large kmalloc.

Re: possible deadlock in blkdev_reread_part

On Wed, Nov 1, 2017 at 10:01 PM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > e19b205be43d11bff638cad4487008c48d21c103 > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler:

Re: [PATCH v2 1/2] fault-inject: Restore support for task-independent fault injection

jection mechanisms: one global (original) and the new local. If one needs global injection, he/she just enables the global one. We don't seem to need the global flag on fault attributes. >> References: commit e41d58185f14 ("fault-inject: support systematic fault >> injecti

Re: scsi: use-after-free in bio_copy_from_iter

On Tue, Dec 6, 2016 at 10:32 AM, Johannes Thumshirn wrote: > On Mon, Dec 05, 2016 at 07:03:39PM +, Al Viro wrote: >> On Mon, Dec 05, 2016 at 04:17:53PM +0100, Johannes Thumshirn wrote: >> > 633 hp = >header; >> > [...] >> > 646 hp->dxferp = (char

Re: scsi: use-after-free in bio_copy_from_iter

On Sat, Dec 3, 2016 at 7:19 PM, Johannes Thumshirn <jthumsh...@suse.de> wrote: > On Sat, Dec 03, 2016 at 04:22:39PM +0100, Dmitry Vyukov wrote: >> On Sat, Dec 3, 2016 at 11:38 AM, Johannes Thumshirn <jthumsh...@suse.de> >> wrote: >> > On Fri, Dec 02, 2016 at 0

scsi: use-after-free in bio_copy_from_iter

Hello, The following program triggers use-after-free in bio_copy_from_iter: https://gist.githubusercontent.com/dvyukov/80cd94b4e4c288f16ee4c787d404118b/raw/10536069562444da51b758bb39655b514ff93b45/gistfile1.txt == BUG: KASAN: