On Sun, Nov 20, 2016 at 10:05:16PM +0100, Richard Weinberger wrote:
> On Sun, Nov 20, 2016 at 10:57 AM, Dmitry Vyukov wrote:
> > On Fri, Nov 18, 2016 at 7:54 PM, Dmitry Vyukov wrote:
> >> On Fri, Nov 18, 2016 at 7:45 PM, Omar Sandoval
On Sun, Nov 20, 2016 at 10:05:16PM +0100, Richard Weinberger wrote:
> On Sun, Nov 20, 2016 at 10:57 AM, Dmitry Vyukov wrote:
> > On Fri, Nov 18, 2016 at 7:54 PM, Dmitry Vyukov wrote:
> >> On Fri, Nov 18, 2016 at 7:45 PM, Omar Sandoval wrote:
> >>> On Fri, Nov 18, 2016 at 11:09:54AM +0100,
On Sun, Nov 20, 2016 at 10:57 AM, Dmitry Vyukov wrote:
> On Fri, Nov 18, 2016 at 7:54 PM, Dmitry Vyukov wrote:
>> On Fri, Nov 18, 2016 at 7:45 PM, Omar Sandoval wrote:
>>> On Fri, Nov 18, 2016 at 11:09:54AM +0100, Dmitry Vyukov wrote:
On Sun, Nov 20, 2016 at 10:57 AM, Dmitry Vyukov wrote:
> On Fri, Nov 18, 2016 at 7:54 PM, Dmitry Vyukov wrote:
>> On Fri, Nov 18, 2016 at 7:45 PM, Omar Sandoval wrote:
>>> On Fri, Nov 18, 2016 at 11:09:54AM +0100, Dmitry Vyukov wrote:
Hello,
The following program triggers GPF in
On Fri, Nov 18, 2016 at 7:54 PM, Dmitry Vyukov wrote:
> On Fri, Nov 18, 2016 at 7:45 PM, Omar Sandoval wrote:
>> On Fri, Nov 18, 2016 at 11:09:54AM +0100, Dmitry Vyukov wrote:
>>> Hello,
>>>
>>> The following program triggers GPF in logfs_alloc_inode:
>>>
On Fri, Nov 18, 2016 at 7:54 PM, Dmitry Vyukov wrote:
> On Fri, Nov 18, 2016 at 7:45 PM, Omar Sandoval wrote:
>> On Fri, Nov 18, 2016 at 11:09:54AM +0100, Dmitry Vyukov wrote:
>>> Hello,
>>>
>>> The following program triggers GPF in logfs_alloc_inode:
>>>
On Fri, Nov 18, 2016 at 7:45 PM, Omar Sandoval wrote:
> On Fri, Nov 18, 2016 at 11:09:54AM +0100, Dmitry Vyukov wrote:
>> Hello,
>>
>> The following program triggers GPF in logfs_alloc_inode:
>>
On Fri, Nov 18, 2016 at 7:45 PM, Omar Sandoval wrote:
> On Fri, Nov 18, 2016 at 11:09:54AM +0100, Dmitry Vyukov wrote:
>> Hello,
>>
>> The following program triggers GPF in logfs_alloc_inode:
>>
On Fri, Nov 18, 2016 at 11:09:54AM +0100, Dmitry Vyukov wrote:
> Hello,
>
> The following program triggers GPF in logfs_alloc_inode:
> https://gist.githubusercontent.com/dvyukov/64a2113e4cb484d9b7e0ef4ff8a522d0/raw/fffdfb8b781ec758563e08765a258da71e6ff2a1/gistfile1.txt
That should be fixed by
On Fri, Nov 18, 2016 at 11:09:54AM +0100, Dmitry Vyukov wrote:
> Hello,
>
> The following program triggers GPF in logfs_alloc_inode:
> https://gist.githubusercontent.com/dvyukov/64a2113e4cb484d9b7e0ef4ff8a522d0/raw/fffdfb8b781ec758563e08765a258da71e6ff2a1/gistfile1.txt
That should be fixed by
Hello,
The following program triggers GPF in logfs_alloc_inode:
https://gist.githubusercontent.com/dvyukov/64a2113e4cb484d9b7e0ef4ff8a522d0/raw/fffdfb8b781ec758563e08765a258da71e6ff2a1/gistfile1.txt
general protection fault: [#1] SMP DEBUG_PAGEALLOC KASAN
Modules linked in:
CPU: 2 PID:
Hello,
The following program triggers GPF in logfs_alloc_inode:
https://gist.githubusercontent.com/dvyukov/64a2113e4cb484d9b7e0ef4ff8a522d0/raw/fffdfb8b781ec758563e08765a258da71e6ff2a1/gistfile1.txt
general protection fault: [#1] SMP DEBUG_PAGEALLOC KASAN
Modules linked in:
CPU: 2 PID:
12 matches
Mail list logo