Messages in this thread | | | Date | Wed, 5 Feb 2003 00:37:38 -0200 (BRST) | From | Rik van Riel <> | Subject | Re: [CHECKER] 112 potential memory leaks in 2.5.48 |
| |
On Tue, 4 Feb 2003, Andy Chou wrote:
> [BUG] Maybe. > /u1/acc/linux/2.5.48/drivers/scsi/scsi_scan.c:1730:scsi_report_lun_scan: > ERROR:LEAK:1706:1730:Memory leak [Allocated from: > /u1/acc/linux/2.5.48/drivers/scsi/scsi_scan.c:1706:scsi_allocate_request]
This one seems fixed in 2.5 current.
> [BUG] > u1/acc/linux/2.5.48/drivers/scsi/sr_ioctl.c:188:sr_do_ioctl: > ERROR:LEAK:85:188:Memory leak [Allocated from: > /u1/acc/linux/2.5.48/drivers/scsi/sr_ioctl.c:85:scsi_allocate_request]
Bug indeed, I've created a patch to fix the possible leak of a scsi request, but can't figure out the bounce buffer logic...
> [BUG] Leaking tmp_ba > /u1/acc/linux/2.5.48/drivers/scsi/st.c:3686:st_attach: > ERROR:LEAK:3704:3686:Memory leak [Allocated from: > /u1/acc/linux/2.5.48/drivers/scsi/st.c:3704:kmalloc]
Doesn't seem to be present in 2.5 current.
> [BUG] [GEM] The case where __dev_get_by_index() returns 0, > followed by goto out. > /u1/acc/linux/2.5.48/net/ipv4/route.c:2229:inet_rtm_getroute: > ERROR:LEAK:2166:2229:Memory leak [Allocated from: > /u1/acc/linux/2.5.48/net/ipv4/route.c:2166:alloc_skb]
Confirmed. I'll take a stab at fixing this one.
Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://guru.conectiva.com/ Current spamtrap: <a href=mailto:"october@surriel.com">october@surriel.com</a> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |