Subject: [merged] drivers-block-paride-pgc-underflow-bug-in-pg_write.patch removed from -mm tree
To: dan.carpenter@xxxxxxxxxx,axboe@xxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Thu, 23 Jan 2014 12:42:42 -0800
The patch titled
Subject: drivers/block/paride/pg.c: underflow bug in pg_write()
has been removed from the -mm tree. Its filename was
drivers-block-paride-pgc-underflow-bug-in-pg_write.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Subject: drivers/block/paride/pg.c: underflow bug in pg_write()
The test here can underflow so we pass bogus lengths to the hardware.
It's a static checker fix and I don't know the impact.
Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Cc: Jens Axboe <axboe@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/block/paride/pg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/block/paride/pg.c~drivers-block-paride-pgc-underflow-bug-in-pg_write drivers/block/paride/pg.c
--- a/drivers/block/paride/pg.c~drivers-block-paride-pgc-underflow-bug-in-pg_write
+++ a/drivers/block/paride/pg.c
@@ -581,7 +581,7 @@ static ssize_t pg_write(struct file *fil
if (hdr.magic != PG_MAGIC)
return -EINVAL;
- if (hdr.dlen > PG_MAX_DATA)
+ if (hdr.dlen < 0 || hdr.dlen > PG_MAX_DATA)
return -EINVAL;
if ((count - hs) > PG_MAX_DATA)
return -EINVAL;
_
Patches currently in -mm which might be from dan.carpenter@xxxxxxxxxx are
origin.patch
drivers-scsi-megaraid-megaraid_mmc-missing-bounds-check-in-mimd_to_kioc.patch
drivers-mailbox-omap-make-mbox-irq-signed-for-error-handling.patch
drivers-vlynq-vlynqc-fix-another-resource-size-off-by-1-error.patch
checkpatch-warn-only-on-space-before-semicolon-at-end-of-line.patch
linux-next.patch
zram-fix-race-between-reset-and-flushing-pending-work.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
