"Aneesh Kumar K.V" writes:
> On 5/14/19 9:45 AM, Dan Williams wrote:
>> [ add Keith who was looking at something similar ]
>>
...
>>
>> If it's reserved then we should not be accessing, even if the above
>> works in practice. Isn't the fix something more like this to fix up
>> the assumptions
On 5/14/19 9:45 AM, Dan Williams wrote:
[ add Keith who was looking at something similar ]
On Mon, May 13, 2019 at 7:54 PM Aneesh Kumar K.V
wrote:
When we initialize the namespace, if we support altmap, we don't initialize all
the
backing struct page where as while releasing the namespace
[ add Keith who was looking at something similar ]
On Mon, May 13, 2019 at 7:54 PM Aneesh Kumar K.V
wrote:
>
> When we initialize the namespace, if we support altmap, we don't initialize
> all the
> backing struct page where as while releasing the namespace we look at some of
> these
On 05/14/2019 08:23 AM, Aneesh Kumar K.V wrote:
> When we initialize the namespace, if we support altmap, we don't initialize
> all the
> backing struct page where as while releasing the namespace we look at some of
> these uninitilized struct page. This results in a kernel crash as below.
Yes
When we initialize the namespace, if we support altmap, we don't initialize all
the
backing struct page where as while releasing the namespace we look at some of
these uninitilized struct page. This results in a kernel crash as below.
kernel BUG at include/linux/mm.h:1034!
cpu 0x2: Vector: 700
