From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [bug report] kmemleak observed with blktests nvme/tcp
Date: Tue, 16 Apr 2024 03:19:41 +0000 [thread overview]
Message-ID: <923a9363-f51b-4fa1-8a0b-003ff46845a2@nvidia.com> (raw)
In-Reply-To: <CAHj4cs8xbBXm1_SKpNpeB5_bbD28YwhorikQ-OYRtt9-Mf+vsQ@mail.gmail.com>
+linux-nvme list for awareness ...
-ck
On 4/6/24 17:38, Yi Zhang wrote:
> Hello
>
> I found the kmemleak issue after blktests nvme/tcp tests on the latest
> linux-block/for-next, please help check it and let me know if you need
> any info/testing for it, thanks.
it will help others to specify which testcase you are using ...
> # dmesg | grep kmemleak
> [ 2580.572467] kmemleak: 92 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
>
> # cat kmemleak.log
> unreferenced object 0xffff8885a1abe740 (size 32):
> comm "kworker/40:1H", pid 799, jiffies 4296062986
> hex dump (first 32 bytes):
> c2 4a 4a 04 00 ea ff ff 00 00 00 00 00 10 00 00 .JJ.............
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace (crc 6328eade):
> [<ffffffffa7f2657c>] __kmalloc+0x37c/0x480
> [<ffffffffa86a9b1f>] sgl_alloc_order+0x7f/0x360
> [<ffffffffc261f6c5>] lo_read_simple+0x1d5/0x5b0 [loop]
> [<ffffffffc26287ef>] 0xffffffffc26287ef
> [<ffffffffc262a2c4>] 0xffffffffc262a2c4
> [<ffffffffc262a881>] 0xffffffffc262a881
> [<ffffffffa76adf3c>] process_one_work+0x89c/0x19f0
> [<ffffffffa76b0813>] worker_thread+0x583/0xd20
> [<ffffffffa76ce2a3>] kthread+0x2f3/0x3e0
> [<ffffffffa74a804d>] ret_from_fork+0x2d/0x70
> [<ffffffffa7406e4a>] ret_from_fork_asm+0x1a/0x30
> unreferenced object 0xffff88a8b03647c0 (size 16):
> comm "kworker/40:1H", pid 799, jiffies 4296062986
> hex dump (first 16 bytes):
> c0 4a 4a 04 00 ea ff ff 00 10 00 00 00 00 00 00 .JJ.............
> backtrace (crc 860ce62b):
> [<ffffffffa7f2657c>] __kmalloc+0x37c/0x480
> [<ffffffffc261f805>] lo_read_simple+0x315/0x5b0 [loop]
> [<ffffffffc26287ef>] 0xffffffffc26287ef
> [<ffffffffc262a2c4>] 0xffffffffc262a2c4
> [<ffffffffc262a881>] 0xffffffffc262a881
> [<ffffffffa76adf3c>] process_one_work+0x89c/0x19f0
> [<ffffffffa76b0813>] worker_thread+0x583/0xd20
> [<ffffffffa76ce2a3>] kthread+0x2f3/0x3e0
> [<ffffffffa74a804d>] ret_from_fork+0x2d/0x70
> [<ffffffffa7406e4a>] ret_from_fork_asm+0x1a/0x30
>
> (gdb) l *(lo_read_simple+0x1d5)
> 0x66c5 is in lo_read_simple (drivers/block/loop.c:284).
> 279 struct bio_vec bvec;
> 280 struct req_iterator iter;
> 281 struct iov_iter i;
> 282 ssize_t len;
> 283
> 284 rq_for_each_segment(bvec, rq, iter) {
> 285 iov_iter_bvec(&i, ITER_DEST, &bvec, 1, bvec.bv_len);
> 286 len = vfs_iter_read(lo->lo_backing_file, &i, &pos, 0);
> 287 if (len < 0)
> 288 return len;
> (gdb) l *(lo_read_simple+0x315)
> 0x6805 is in lo_read_simple (./include/linux/bio.h:120).
> 115 iter->bi_sector += bytes >> 9;
> 116
> 117 if (bio_no_advance_iter(bio))
> 118 iter->bi_size -= bytes;
> 119 else
> 120 bvec_iter_advance_single(bio->bi_io_vec, iter, bytes);
> 121 }
> 122
> 123 void __bio_advance(struct bio *, unsigned bytes);
> 124
>
>
-ck
next parent reply other threads:[~2024-04-16 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHj4cs8xbBXm1_SKpNpeB5_bbD28YwhorikQ-OYRtt9-Mf+vsQ@mail.gmail.com>
2024-04-16 3:19 ` Chaitanya Kulkarni [this message]
2024-04-19 1:04 ` [bug report] kmemleak observed with blktests nvme/tcp Yi Zhang
2024-04-21 10:31 ` Sagi Grimberg
2024-04-22 4:59 ` Yi Zhang
2024-04-22 10:46 ` Sagi Grimberg
2024-04-24 6:18 ` Yi Zhang
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=923a9363-f51b-4fa1-8a0b-003ff46845a2@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=yi.zhang@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).