mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Li Zetao <lizetao1@huawei.com>
Cc: 3chas3@gmail.com, linux-atm-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	romieu@fr.zoreil.com
Subject: Re: [PATCH v2] atm: idt77252: fix kmemleak when rmmod idt77252
Date: Wed, 22 Mar 2023 04:20:17 +0000	[thread overview]
Message-ID: <167945881756.16584.2824605929360811785.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230320143318.2644630-1-lizetao1@huawei.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 20 Mar 2023 14:33:18 +0000 you wrote:
> There are memory leaks reported by kmemleak:
> 
>   unreferenced object 0xffff888106500800 (size 128):
>     comm "modprobe", pid 1017, jiffies 4297787785 (age 67.152s)
>     hex dump (first 32 bytes):
>       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
>       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
>     backtrace:
>       [<00000000970ce626>] __kmem_cache_alloc_node+0x20c/0x380
>       [<00000000fb5f78d9>] kmalloc_trace+0x2f/0xb0
>       [<000000000e947e2a>] idt77252_init_one+0x2847/0x3c90 [idt77252]
>       [<000000006efb048e>] local_pci_probe+0xeb/0x1a0
>     ...
> 
> [...]

Here is the summary with links:
  - [v2] atm: idt77252: fix kmemleak when rmmod idt77252
    https://git.kernel.org/netdev/net/c/4fe3c88552a3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-03-22  4:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  3:52 [PATCH] " Li Zetao
2023-03-19  0:28 ` Francois Romieu
2023-03-20 14:33 ` [PATCH v2] " Li Zetao
2023-03-22  4:20   ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=167945881756.16584.2824605929360811785.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=3chas3@gmail.com \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizetao1@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®