On 04/19/2018 04:35 PM, Andrey Ryabinin wrote:
>
>
> On 04/18/2018 09:37 PM, Linus Torvalds wrote:
>> Ugh, that lustre code is disgusting.
>>
>> I thought we were getting rid of it.
>>
>> Anyway, I started looking at why the stack trace is such an incredi
On 04/18/2018 09:37 PM, Linus Torvalds wrote:
> Ugh, that lustre code is disgusting.
>
> I thought we were getting rid of it.
>
> Anyway, I started looking at why the stack trace is such an incredible
> mess, with lots of stale entries.
>
> The reason (well, _one_ reason) seems to be
flag preventing guard hole allocation)
Signed-off-by: Andrey Ryabinin a.ryabi...@samsung.com
Reported-by: Amit Pundir amit.pun...@linaro.org
---
drivers/android/binder.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/android/binder.c b/drivers/android/binder.c
flag preventing guard hole allocation)
Signed-off-by: Andrey Ryabinin a.ryabi...@samsung.com
Reported-by: Amit Pundir amit.pun...@linaro.org
---
Changes since v1:
- fixed ret check after map_kernel_ranges_noflush().
drivers/android/binder.c | 10 +-
1 file changed, 5 insertions(+), 5
On 02/27/2015 08:26 PM, John Stultz wrote:
On Fri, Feb 27, 2015 at 8:30 AM, Andrey Ryabinin a.ryabi...@samsung.com
wrote:
binder_update_page_range() initializes only addr and size
fields in 'struct vm_struct tmp_area;' and passes it to
map_vm_area().
Before 71394fe50146 (mm: vmalloc: add
