On Wed, Nov 28, 2018 at 5:21 AM Qian Cai wrote:
> On 11/10/18 11:59 AM, Catalin Marinas wrote:
> > On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
> >> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
> >>> The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
> >>>
On Wed, Nov 28, 2018 at 5:21 AM Qian Cai wrote:
> On 11/10/18 11:59 AM, Catalin Marinas wrote:
> > On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
> >> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
> >>> The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
> >>>
On 11/10/18 11:59 AM, Catalin Marinas wrote:
> On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
>> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
>>> The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
>>> disables kmemleak every time on this aarch64 server running
On 11/10/18 11:59 AM, Catalin Marinas wrote:
> On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
>> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
>>> The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
>>> disables kmemleak every time on this aarch64 server running
> On Nov 10, 2018, at 12:42 PM, Qian Cai wrote:
>
>
> On 11/10/18 at 11:59 AM, Catalin Marinas wrote:
>
>> On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
>>> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
> On Nov 10, 2018, at 12:42 PM, Qian Cai wrote:
>
>
> On 11/10/18 at 11:59 AM, Catalin Marinas wrote:
>
>> On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
>>> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
On 11/10/18 at 11:59 AM, Catalin Marinas wrote:
> On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
> > On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
> > > The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
> > > disables kmemleak every time on this aarch64 server
On 11/10/18 at 11:59 AM, Catalin Marinas wrote:
> On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
> > On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
> > > The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
> > > disables kmemleak every time on this aarch64 server
On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
> > The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
> > disables kmemleak every time on this aarch64 server running the latest
> > mainline
> > (b00d209).
> >
> > #
On Sat, Nov 10, 2018 at 10:08:10AM -0500, Qian Cai wrote:
> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
> > The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
> > disables kmemleak every time on this aarch64 server running the latest
> > mainline
> > (b00d209).
> >
> > #
> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
>
> The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
> disables kmemleak every time on this aarch64 server running the latest
> mainline
> (b00d209).
>
> # echo scan > /sys/kernel/debug/kmemleak
> -bash: echo: write
> On Nov 8, 2018, at 4:23 PM, Qian Cai wrote:
>
> The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
> disables kmemleak every time on this aarch64 server running the latest
> mainline
> (b00d209).
>
> # echo scan > /sys/kernel/debug/kmemleak
> -bash: echo: write
The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
disables kmemleak every time on this aarch64 server running the latest mainline
(b00d209).
# echo scan > /sys/kernel/debug/kmemleakÂ
-bash: echo: write error: Device or resource busy
Any idea on how to enable kmemleak
The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 4, so it
disables kmemleak every time on this aarch64 server running the latest mainline
(b00d209).
# echo scan > /sys/kernel/debug/kmemleakÂ
-bash: echo: write error: Device or resource busy
Any idea on how to enable kmemleak
14 matches
Mail list logo