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 y

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 >> affect the data format passed

Re: WARNING in ext4_invalidatepage

2018-10-16 Thread Theodore Y. Ts'o
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 > affect the data format passed in. The problem is that putting something which is simply and

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 >> 0x6611 is in fact EXT4_IOC_SWAP

Re: WARNING in ext4_invalidatepage

2018-10-15 Thread Theodore Y. Ts'o
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 > 0x6611 is in fact EXT4_IOC_SWAP_BOOT. So I think it's this one: > > 05:23:28 executing progra

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', 0x0) >> socketpair$unix(0x1, 0x1, 0x0,

Re: WARNING in ext4_invalidatepage

2018-10-08 Thread Theodore Y. Ts'o
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', 0x0) > socketpair$unix(0x1, 0x1, 0x0, &(0x7f000380)={0x, > 0x}) >

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: h

WARNING in ext4_invalidatepage

2018-10-08 Thread syzbot
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: https://syzkaller.appspot.com/x/.config?x=c0af03fe452b65fb da