Hi,
On Tue, Jul 31, 2018 at 10:38:06AM +0200, Johannes Thumshirn wrote:
> So I've fixed one use-after-free and one memory leak, but the one you
> reported is still on the TODO list.
Wow, thanks...
> Long story short, I can reproduce it here and I'm working on it.
>
> Thanks for your patience,
On Fri, Jul 27, 2018 at 12:49:55AM +0200, ard wrote:
> Actually already got there from my arm dump, but they are different in
> backtrace.
> Anyway:
> root@antec:~# grep -c fc_rport_create kmemleak.txt
> 44
> So 44 * 512 bytes leaked in that path. And an extra thing: "it was leaked in"
> libfc
On Fri, Jul 27, 2018 at 12:49:55AM +0200, ard wrote:
> Hi,
>
> On Thu, Jul 26, 2018 at 05:05:37PM +0200, Johannes Thumshirn wrote:
> > On Thu, Jul 26, 2018 at 04:25:24PM +0200, ard wrote:
> > > The system itself is an exynos 5422 arm. It worked perfectly fine
> > > with 3.10 as an Initiator, now
Hi,
On Thu, Jul 26, 2018 at 05:05:37PM +0200, Johannes Thumshirn wrote:
> On Thu, Jul 26, 2018 at 04:25:24PM +0200, ard wrote:
> > The system itself is an exynos 5422 arm. It worked perfectly fine
> > with 3.10 as an Initiator, now it leaks memory the moment I
> > enable the FCoE vlan on the
On Thu, Jul 26, 2018 at 04:25:24PM +0200, ard wrote:
> The system itself is an exynos 5422 arm. It worked perfectly fine
> with 3.10 as an Initiator, now it leaks memory the moment I
> enable the FCoE vlan on the port.
So I had a look through the commits between v3.10 and v4.14 and this
one
On Thu, Jul 26, 2018 at 04:25:24PM +0200, ard wrote:
> > Anyways, can you please enable the kernel memory leak detector [1] and
> > possibly even try a more up to date (like v4.18-rc6) kernel?
> >
> > [1] https://www.kernel.org/doc/html/v4.17/dev-tools/kmemleak.html
>
> The up to date kernel
> On Mon, Jul 23, 2018 at 02:16:31PM +0200, ard wrote:
> > Date: Mon, 23 Jul 2018 14:16:31 +0200
> > From: ard
> > Subject: FCOE vn2vn memory leaks in 4.14
> > To: fcoe-de...@open-fcoe.org
> >
> > Hi guys,
> >
> > After an upgrade of one of my s
02:16:31PM +0200, ard wrote:
> Date: Mon, 23 Jul 2018 14:16:31 +0200
> From: ard
> Subject: FCOE vn2vn memory leaks in 4.14
> To: fcoe-de...@open-fcoe.org
>
> Hi guys,
>
> After an upgrade of one of my systems from 3.10 to 4.14.55, I
> noticed a serious memory leak.
Hi Guys,
I sent this to fcoe-devel but it might be holiday season or the
mailing list is abandoned as the emails concerning fcoe are
pretty low.
On Mon, Jul 23, 2018 at 02:16:31PM +0200, ard wrote:
Date: Mon, 23 Jul 2018 14:16:31 +0200
From: ard
Subject: FCOE vn2vn memory leaks in 4.14
To: fcoe
9 matches
Mail list logo
