The patch titled ioremap balanced with iounmap for drivers/scsi/fdomain.c has been added to the -mm tree. Its filename is ioremap-balanced-with-iounmap-drivers-scsi-fdomainc.patch See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: ioremap balanced with iounmap for drivers/scsi/fdomain.c From: Amol Lad <amol@xxxxxxxxxxxxxxxxxxx> ioremap must be balanced by an iounmap and failing to do so can result in a memory leak. Signed-off-by: Amol Lad <amol@xxxxxxxxxxxxxxxxxxx> Cc: James Bottomley <James.Bottomley@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- drivers/scsi/fdomain.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff -puN drivers/scsi/fdomain.c~ioremap-balanced-with-iounmap-drivers-scsi-fdomainc drivers/scsi/fdomain.c --- a/drivers/scsi/fdomain.c~ioremap-balanced-with-iounmap-drivers-scsi-fdomainc +++ a/drivers/scsi/fdomain.c @@ -780,7 +780,11 @@ found: else printk( " FAILURE\n" ); #endif - if (!flag) return 0; /* iobase not found */ + if (!flag) { + if (bios_mem) + iounmap(bios_mem); + return 0; /* iobase not found */ + } *irq = fdomain_get_irq( base ); *iobase = base; _ Patches currently in -mm which might be from amol@xxxxxxxxxxxxxxxxxxx are origin.patch ioremap-balanced-with-iounmap-drivers-scsi-zalonc.patch ioremap-balanced-with-iounmap-drivers-scsi-sun3_scsic.patch ioremap-balanced-with-iounmap-drivers-scsi-sun3_scsi_vmec.patch ioremap-balanced-with-iounmap-drivers-scsi-seagatec.patch ioremap-balanced-with-iounmap-drivers-scsi-qlogicptic.patch ioremap-balanced-with-iounmap-drivers-scsi-nsp32c.patch ioremap-balanced-with-iounmap-drivers-scsi-ncr53c8xxc.patch ioremap-balanced-with-iounmap-drivers-scsi-fdomainc.patch ioremap-balanced-with-iounmap-drivers-scsi-amiga7xxc.patch ioremap-balanced-with-iounmap-drivers-scsi-3w-9xxxc.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html