On Thu, Oct 01, 2020 at 12:23:08PM +0200, Dmitry Vyukov wrote:
> I've prepared a change that removes rodata=n:
> https://github.com/google/syzkaller/pull/2155
Looks good.
> I think we will be able to indirectly evaluate if it helps or not over
> some period of time based on occurrence of any new
On Wed, Sep 30, 2020 at 6:31 PM Borislav Petkov wrote:
>
> On Wed, Sep 30, 2020 at 06:23:44PM +0200, Dmitry Vyukov wrote:
> > Here is the answer:
> > https://github.com/google/syzkaller/blob/master/tools/create-gce-image.sh#L189
> >
> > # rodata=n: mark_rodata_ro becomes very slow with KASAN (lots
On Wed, Sep 30, 2020 at 06:23:44PM +0200, Dmitry Vyukov wrote:
> Here is the answer:
> https://github.com/google/syzkaller/blob/master/tools/create-gce-image.sh#L189
>
> # rodata=n: mark_rodata_ro becomes very slow with KASAN (lots of PGDs)
>
> I have some vague memory that there was some debug d
On Wed, Sep 30, 2020 at 6:23 PM Dmitry Vyukov wrote:
> > Hi,
> >
> > one more thing I just spotted. The default install of syzkaller here
> > runs the guest with this on the kernel command line:
> >
> > 2020/09/30 17:56:18 running command: qemu-system-x86_64 []string{"-m",
> > "2048",
> > "-smp",
On Wed, Sep 30, 2020 at 6:17 PM Borislav Petkov wrote:
>
> Hi,
>
> one more thing I just spotted. The default install of syzkaller here
> runs the guest with this on the kernel command line:
>
> 2020/09/30 17:56:18 running command: qemu-system-x86_64 []string{"-m", "2048",
> "-smp", "2", "-display
Hi,
one more thing I just spotted. The default install of syzkaller here
runs the guest with this on the kernel command line:
2020/09/30 17:56:18 running command: qemu-system-x86_64 []string{"-m", "2048",
"-smp", "2", "-display", ... "-append", "earlyprintk=serial oops=panic ...
nmi_watchdog=pan
On Tue, Sep 29, 2020 at 10:33 AM Borislav Petkov wrote:
>
> On Mon, Sep 28, 2020 at 10:23:53PM +0200, Borislav Petkov wrote:
> > 2020/09/28 22:21:01 VMs 3, executed 179, corpus cover 11792, corpus signal
> > 10881, max signal 19337, crashes 0, repro 0
>
> Ok, so far triggered two things:
>
> WARN
On Mon, Sep 28, 2020 at 10:33 PM Nick Desaulniers
wrote:
>
> On Sun, Sep 27, 2020 at 10:18 PM 'Dmitry Vyukov' via Clang Built Linux
> wrote:
> >
> > On Sun, Sep 27, 2020 at 4:57 PM Borislav Petkov wrote:
> > >
> > > On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> > > > Hello,
> > > >
>
On Mon, Sep 28, 2020 at 10:23:53PM +0200, Borislav Petkov wrote:
> 2020/09/28 22:21:01 VMs 3, executed 179, corpus cover 11792, corpus signal
> 10881, max signal 19337, crashes 0, repro 0
Ok, so far triggered two things:
WARNING in f2fs_is_valid_blkaddr1 2020/09/29 10:27
re
> On Sep 28, 2020, at 1:52 PM, Nick Desaulniers wrote:
>
> On Mon, Sep 28, 2020 at 3:34 AM 'Dmitry Vyukov' via Clang Built Linux
> wrote:
>>
>>> On Mon, Sep 28, 2020 at 10:54 AM Borislav Petkov wrote:
>>>
>>> On Mon, Sep 28, 2020 at 10:40:19AM +0200, Dmitry Vyukov wrote:
I meant the k
On Mon, Sep 28, 2020 at 3:34 AM 'Dmitry Vyukov' via Clang Built Linux
wrote:
>
> On Mon, Sep 28, 2020 at 10:54 AM Borislav Petkov wrote:
> >
> > On Mon, Sep 28, 2020 at 10:40:19AM +0200, Dmitry Vyukov wrote:
> > > I meant the kernel self-corrupts itself, that just wasn't detected by
> > > KASAN,
On Sun, Sep 27, 2020 at 10:18 PM 'Dmitry Vyukov' via Clang Built Linux
wrote:
>
> On Sun, Sep 27, 2020 at 4:57 PM Borislav Petkov wrote:
> >
> > On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:92ab97
On Mon, Sep 28, 2020 at 12:33:57PM +0200, Dmitry Vyukov wrote:
> It may be related to VMs, but also may well not be related to VMs.
Right, and so I tried to set it up on a test box here, it looks like
it worked, see below. I'll let it fuzz in the coming days and see what
explodes...
2020/09/28 22
On Mon, Sep 28, 2020 at 10:54 AM Borislav Petkov wrote:
>
> On Mon, Sep 28, 2020 at 10:40:19AM +0200, Dmitry Vyukov wrote:
> > I meant the kernel self-corrupts itself, that just wasn't detected by
> > KASAN, page protections, etc.
>
> Well, Nick already asked this but we're marking all kernel text
On Mon, Sep 28, 2020 at 10:40:19AM +0200, Dmitry Vyukov wrote:
> I meant the kernel self-corrupts itself, that just wasn't detected by
> KASAN, page protections, etc.
Well, Nick already asked this but we're marking all kernel text RO early
during boot. So it either is happening before that or some
On Mon, Sep 28, 2020 at 10:38 AM Borislav Petkov wrote:
>
> On Mon, Sep 28, 2020 at 08:06:19AM +0200, Dmitry Vyukov wrote:
> > Maybe it's just a random silent memory corruption in the end?...
>
> Oh, the rabbit hole goes deeper. But if it is corruption, what is the
> common element in all those? A
On Mon, Sep 28, 2020 at 08:06:19AM +0200, Dmitry Vyukov wrote:
> Maybe it's just a random silent memory corruption in the end?...
Oh, the rabbit hole goes deeper. But if it is corruption, what is the
common element in all those? All those guests have run on the same
physical machine?
If so, you p
On Mon, 28 Sep 2020 at 07:18, Dmitry Vyukov wrote:
>
> On Sun, Sep 27, 2020 at 4:57 PM Borislav Petkov wrote:
> >
> > On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:92ab97ad Merge tag 'sh-for-5.9-pa
On Mon, Sep 28, 2020 at 7:18 AM Dmitry Vyukov wrote:
> > On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:92ab97ad Merge tag 'sh-for-5.9-part2' of
> > > git://git.libc.or..
> > > git tree: upstr
On Sun, Sep 27, 2020 at 4:57 PM Borislav Petkov wrote:
>
> On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:92ab97ad Merge tag 'sh-for-5.9-part2' of git://git.libc.or..
> > git tree: upstream
> > console o
On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:92ab97ad Merge tag 'sh-for-5.9-part2' of git://git.libc.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1069669b90
> kernel
On Fri, Sep 25, 2020 at 05:32:14PM -0700, Nick Desaulniers wrote:
> Boris, one question I have. Doesn't the kernel mark pages backing
> executable code as read only at some point?
Yes, I added some debug output:
[ 562.959995][T1] Freeing unused kernel image (initmem) memory: 2548K
[ 563.672
On Sat, Sep 26, 2020 at 1:21 PM Borislav Petkov wrote:
>
> On Wed, Sep 23, 2020 at 05:20:06PM +0200, Dmitry Vyukov wrote:
> > It's a random fuzzing workload. You can get this workload by running
> > syzkaller locally:
> > https://github.com/google/syzkaller/blob/master/docs/linux/setup_ubuntu-host
On Wed, Sep 23, 2020 at 05:20:06PM +0200, Dmitry Vyukov wrote:
> It's a random fuzzing workload. You can get this workload by running
> syzkaller locally:
> https://github.com/google/syzkaller/blob/master/docs/linux/setup_ubuntu-host_qemu-vm_x86-64-kernel.md
Yeah, the my.cfg example suggests that
On Sat, Sep 26, 2020 at 2:32 AM 'Nick Desaulniers' via syzkaller-bugs
wrote:
> > > > On Wed, Sep 23, 2020 at 11:24:48AM +0200, Dmitry Vyukov wrote:
> > > > > 3. Run syzkaller locally with custom patches.
> > > >
> > > > Let's say I wanna build the kernel with clang-10 using your .config and
> > >
On Fri, Sep 25, 2020 at 5:22 AM Dmitry Vyukov wrote:
>
> On Wed, Sep 23, 2020 at 5:20 PM Dmitry Vyukov wrote:
> >
> > On Wed, Sep 23, 2020 at 12:34 PM Borislav Petkov wrote:
> > >
> > > On Wed, Sep 23, 2020 at 11:24:48AM +0200, Dmitry Vyukov wrote:
> > > > 3. Run syzkaller locally with custom pa
On Wed, Sep 23, 2020 at 5:20 PM Dmitry Vyukov wrote:
>
> On Wed, Sep 23, 2020 at 12:34 PM Borislav Petkov wrote:
> >
> > On Wed, Sep 23, 2020 at 11:24:48AM +0200, Dmitry Vyukov wrote:
> > > 3. Run syzkaller locally with custom patches.
> >
> > Let's say I wanna build the kernel with clang-10 usin
On Wed, Sep 23, 2020 at 12:34 PM Borislav Petkov wrote:
>
> On Wed, Sep 23, 2020 at 11:24:48AM +0200, Dmitry Vyukov wrote:
> > 3. Run syzkaller locally with custom patches.
>
> Let's say I wanna build the kernel with clang-10 using your .config and
> run it in a vm locally. What are the steps in o
On Wed, Sep 23, 2020 at 11:24:48AM +0200, Dmitry Vyukov wrote:
> 3. Run syzkaller locally with custom patches.
Let's say I wanna build the kernel with clang-10 using your .config and
run it in a vm locally. What are the steps in order to reproduce the
same workload syzkaller runs in the guest on t
On Wed, Sep 23, 2020 at 11:03 AM Borislav Petkov wrote:
>
> On Tue, Sep 22, 2020 at 11:56:04AM -0700, Nick Desaulniers wrote:
> > So I think there's an issue with "deterministically reproducible."
> > The syzcaller report has:
> > > > Unfortunately, I don't have any reproducer for this issue yet.
On Tue, Sep 22, 2020 at 11:56:04AM -0700, Nick Desaulniers wrote:
> So I think there's an issue with "deterministically reproducible."
> The syzcaller report has:
> > > Unfortunately, I don't have any reproducer for this issue yet.
Yeah, Dmitry gave two other links of similar reports, the first on
On Tue, Sep 22, 2020 at 11:56:04AM -0700, Nick Desaulniers wrote:
> > Gnight and good luck.
>
> Ah, that's a famous quote from journalist Edward R Murrow, who helped
> defeat Senator Joseph McCarthy (Murrow's show See It Now dedicated a
> segment to addressing McCarthy).
Good. Finally someone has
On Mon, Sep 21, 2020 at 3:13 PM Borislav Petkov wrote:
>
> On Mon, Sep 21, 2020 at 01:59:43PM -0700, Nick Desaulniers wrote:
> > Right, the two sequences above look almost the same, except those 4
> > bytes of zeros (the disassembler gets confused about the rest, but
> > it's the same byte sequenc
On Mon, Sep 21, 2020 at 10:59 PM 'Nick Desaulniers' via syzkaller-bugs
wrote:
>
> On Mon, Sep 21, 2020 at 1:09 AM 'Dmitry Vyukov' via Clang Built Linux
> wrote:
> >
> > On Mon, Sep 21, 2020 at 7:54 AM Dmitry Vyukov wrote:
> > >
> > > On Sat, Sep 19, 2020 at 1:08 PM Borislav Petkov wrote:
> > >
On Mon, Sep 21, 2020 at 10:59 PM 'Nick Desaulniers' via syzkaller-bugs
wrote:
>
> On Mon, Sep 21, 2020 at 1:09 AM 'Dmitry Vyukov' via Clang Built Linux
> wrote:
> >
> > On Mon, Sep 21, 2020 at 7:54 AM Dmitry Vyukov wrote:
> > >
> > > On Sat, Sep 19, 2020 at 1:08 PM Borislav Petkov wrote:
> > >
On Mon, Sep 21, 2020 at 01:59:43PM -0700, Nick Desaulniers wrote:
> Right, the two sequences above look almost the same, except those 4
> bytes of zeros (the disassembler gets confused about the rest, but
> it's the same byte sequence otherwise). Are the two disassemblies a
> comparison of the cod
On Mon, Sep 21, 2020 at 1:09 AM 'Dmitry Vyukov' via Clang Built Linux
wrote:
>
> On Mon, Sep 21, 2020 at 7:54 AM Dmitry Vyukov wrote:
> >
> > On Sat, Sep 19, 2020 at 1:08 PM Borislav Petkov wrote:
> > >
> > > On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> > > > Hello,
> > > >
> > > >
On Mon, Sep 21, 2020 at 7:54 AM Dmitry Vyukov wrote:
>
> On Sat, Sep 19, 2020 at 1:08 PM Borislav Petkov wrote:
> >
> > On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:92ab97ad Merge tag 'sh-for-5.9-
On Sat, Sep 19, 2020 at 1:08 PM Borislav Petkov wrote:
>
> On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:92ab97ad Merge tag 'sh-for-5.9-part2' of git://git.libc.or..
> > git tree: upstream
> > console o
On Sat, Sep 19, 2020 at 01:32:14AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:92ab97ad Merge tag 'sh-for-5.9-part2' of git://git.libc.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1069669b90
> kernel
Hello,
syzbot found the following issue on:
HEAD commit:92ab97ad Merge tag 'sh-for-5.9-part2' of git://git.libc.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1069669b90
kernel config: https://syzkaller.appspot.com/x/.config?x=cd992d74d6c7e62
dash
41 matches
Mail list logo
