From: Md Muazzam Husain <mdmuazzamhusain@gmail.com>
To: penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mdakhil2003@gmail.com
Subject: Slab bug during skb allocation
Date: Thu, 10 Dec 2020 23:25:13 +0530 [thread overview]
Message-ID: <CAFQRB7rA6hHc_f8O7qJVn2ufrp_i0PQyTJ4OsNwzyahV5Uq+Jg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
Hi All,
I have kernel version 3.10.59. So during the allocation for skb i
am getting call trace for __netdev_alloc_skb which follows
till cache_alloc_refill and finally crashes. Please find snapshot below.
addr2line -e vmlinux ffffffffc114109c shows linux/mm/slab.c:2700 has the
problem. Is there any existing bug and any patch for this.
Call Trace:
[<ffffffffc114109c>] *cache_alloc_refill*+0x1b4/0x848
[<ffffffffc1141854>] __kmalloc_track_caller+0x124/0x1f0
[<ffffffffc144a930>] __kmalloc_reserve.isra.17+0x40/0xa8
[<ffffffffc144b644>] __alloc_skb+0x84/0x1a0
[<ffffffffc144d084>] *__netdev_alloc_skb*+0xdc/0x148
[<ffffffffc13fb510>] xlpnae_irq+0x148/0x200
[<ffffffffc10b87ac>] handle_irq_event_percpu+0x94/0x3f0
[<ffffffffc10b8b5c>] handle_irq_event+0x54/0x98
[<ffffffffc10bc724>] handle_level_irq+0xe4/0x170
[<ffffffffc10b7d90>] generic_handle_irq+0x38/0x58
[<ffffffffc1018a20>] do_IRQ+0x18/0x28
[<ffffffffc1015ce8>] plat_irq_dispatch+0x258/0x490
[<ffffffffc1016a00>] ret_from_irq+0x0/0x4
[<ffffffffc1016ca0>] __r4k_wait+0x20/0x40
[<ffffffffc109072c>] cpu_startup_entry+0xd4/0x2d8
[<ffffffffc1014ab8>] prom_pre_boot_secondary_cpus+0x0/0x48
Thanks,
Muazzam
[-- Attachment #2: Type: text/html, Size: 1485 bytes --]
next reply other threads:[~2020-12-10 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 17:55 Md Muazzam Husain [this message]
2020-12-10 18:12 ` Matthew Wilcox
2020-12-10 19:06 ` Md Muazzam Husain
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=CAFQRB7rA6hHc_f8O7qJVn2ufrp_i0PQyTJ4OsNwzyahV5Uq+Jg@mail.gmail.com \
--to=mdmuazzamhusain@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mdakhil2003@gmail.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.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