Re: [PATCHv2] kmemleak: Add option to print warnings to dmesg

2018-08-31 Thread Catalin Marinas
On Thu, Aug 30, 2018 at 09:43:27AM +0200, Vincent Whitchurch wrote: > On Tue, Aug 28, 2018 at 11:26:22AM +0100, Catalin Marinas wrote: > > On Tue, Aug 28, 2018 at 12:14:12PM +0200, Vincent Whitchurch wrote: > > > On Mon, Aug 27, 2018 at 03:16:41PM -0700, Andrew Morton wrote: > > > > On Mon, 27 Aug

Re: [PATCHv2] kmemleak: Add option to print warnings to dmesg

2018-08-30 Thread Vincent Whitchurch
On Tue, Aug 28, 2018 at 11:26:22AM +0100, Catalin Marinas wrote: > On Tue, Aug 28, 2018 at 12:14:12PM +0200, Vincent Whitchurch wrote: > > On Mon, Aug 27, 2018 at 03:16:41PM -0700, Andrew Morton wrote: > > > On Mon, 27 Aug 2018 10:38:21 +0200 Vincent Whitchurch > > > wrote: > > > > +config DEBUG_

Re: [PATCHv2] kmemleak: Add option to print warnings to dmesg

2018-08-28 Thread Catalin Marinas
On Tue, Aug 28, 2018 at 12:14:12PM +0200, Vincent Whitchurch wrote: > On Mon, Aug 27, 2018 at 03:16:41PM -0700, Andrew Morton wrote: > > On Mon, 27 Aug 2018 10:38:21 +0200 Vincent Whitchurch > > wrote: > > > --- a/lib/Kconfig.debug > > > +++ b/lib/Kconfig.debug > > > @@ -593,6 +593,15 @@ config D

Re: [PATCHv2] kmemleak: Add option to print warnings to dmesg

2018-08-28 Thread Vincent Whitchurch
On Mon, Aug 27, 2018 at 03:16:41PM -0700, Andrew Morton wrote: > On Mon, 27 Aug 2018 10:38:21 +0200 Vincent Whitchurch > wrote: > > > Currently, kmemleak only prints the number of suspected leaks to dmesg > > but requires the user to read a debugfs file to get the actual stack > > traces of the

Re: [PATCHv2] kmemleak: Add option to print warnings to dmesg

2018-08-27 Thread Andrew Morton
On Mon, 27 Aug 2018 10:38:21 +0200 Vincent Whitchurch wrote: > Currently, kmemleak only prints the number of suspected leaks to dmesg > but requires the user to read a debugfs file to get the actual stack > traces of the objects' allocation points. Add an option to print the > full object infor

[PATCHv2] kmemleak: Add option to print warnings to dmesg

2018-08-27 Thread Vincent Whitchurch
Currently, kmemleak only prints the number of suspected leaks to dmesg but requires the user to read a debugfs file to get the actual stack traces of the objects' allocation points. Add an option to print the full object information to dmesg too. This allows easier integration of kmemleak into au