Hi all,
I am failed to reproduce it on target kernel with the reproducer file
or replaying the target syzkaller description log file, do I made
something wrong or there exists more subjects then the line in
repro.txt:
#{Threaded:true Collide:true Repeat:false Procs:1 Sandbox:namespace
Fault:false
Maybe I have just made some mistakes on understanding the reproduction
methods, will try it again.
Thanks,
- ChunYu
On Thu, Oct 26, 2017 at 10:49 PM, Dmitry Vyukov wrote:
> On Thu, Oct 26, 2017 at 10:53 AM, ChunYu Wang wrote:
>> Hi all,
>>
>> I am failed to reproduce it
Hi GeneBlue,
Thanks for this reporting, do you have any logs related to the bug and
could find the syscalls enabled for fuzzing during triggering this
bug? I do not think it is not reproducible, but first, it needs some
inspections manually.
- ChunYu
On Thu, Sep 14, 2017 at 7:54 PM, GeneBlue w
On Fri, Sep 15, 2017 at 12:41 AM, Andreas Dilger wrote:
> I don't think a reproducer is needed. It looks like the fsync callpath
> is happening from an IRQ context due to IO completion, and then re-entering
> the filesystem while a transaction is already started. It looks like the
> original IO
e_idle_call kernel/sched/idle.c:155 [inline]
>>> do_idle+0x230/0x380 kernel/sched/idle.c:244
>>> cpu_startup_entry+0x18/0x20 kernel/sched/idle.c:346
>>> start_secondary+0x2a7/0x340 arch/x86/kernel/smpboot.c:275
>>> start_cpu+0x14/0x14 arch/x86/kernel/head_64.S:306
>>> Code: Bad RIP value.
>>> RIP: (null) RSP: 88006d1077c8
>>> CR2:
>>> ---[ end trace 845120b8a0d21411 ]---
>>>
>>> On commit 093b995e3b55a0ae0670226ddfcb05bfbf0099ae
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "syzkaller" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to syzkaller+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
--
CHUNYU WANG
ASSOCIATE QE
KERNEL ENG
5 matches
Mail list logo
