On Wed, Jun 27, 2018 at 09:09:40AM +0200, Christoph Hellwig wrote:
> Al, can you pick up this fix from Chunyu?
Applied.
inux-fsde...@vger.kernel.org,
> > linux-kernel@vger.kernel.org
> > Sent: Monday, June 11, 2018 2:23:54 PM
> > Subject: Re: [PATCH] proc: add proc_seq_release
> >
> > On Sun, Jun 10, 2018 at 03:51:24AM +0800, Chunyu Hu wrote:
> > > kmemleak reported some memory leak on rea
- Original Message -
> From: "Christoph Hellwig"
> To: "Chunyu Hu"
> Cc: v...@zeniv.linux.org.uk, h...@lst.de, linux-fsde...@vger.kernel.org,
> linux-kernel@vger.kernel.org
> Sent: Monday, June 11, 2018 2:23:54 PM
> Subject: Re: [PATCH] proc: ad
On Sun, Jun 10, 2018 at 03:51:24AM +0800, Chunyu Hu wrote:
> kmemleak reported some memory leak on reading proc files. After adding
> some debug lines, find that proc_seq_fops is using seq_release as
> release handler, which won't handle the free of 'private' field of
> seq_file, while in fact the
kmemleak reported some memory leak on reading proc files. After adding
some debug lines, find that proc_seq_fops is using seq_release as
release handler, which won't handle the free of 'private' field of
seq_file, while in fact the open handler proc_seq_open could create
the private data with __seq
5 matches
Mail list logo