The patch titled aoe: ignore vendor extension AoE responses has been removed from the -mm tree. Its filename was aoe-ignore-vendor-extension-aoe-responses.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: aoe: ignore vendor extension AoE responses From: Ed Cashin <ecashin@xxxxxxxxxx> The Welland ME-747K-SI AoE target generates unsolicited AoE responses that are marked as vendor extensions. Instead of ignoring these packets, the aoe driver was generating kernel messages for each unrecognized response received. This patch corrects the behavior. Signed-off-by: Ed Cashin <ecashin@xxxxxxxxxx> Reported-by: <karaluh@xxxxxxxxxx> Tested-by: <karaluh@xxxxxxxxxx> Cc: <stable@xxxxxxxxxx> Cc: Alex Buell <alex.buell@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/block/aoe/aoe.h | 1 + drivers/block/aoe/aoenet.c | 2 ++ 2 files changed, 3 insertions(+) diff -puN drivers/block/aoe/aoe.h~aoe-ignore-vendor-extension-aoe-responses drivers/block/aoe/aoe.h --- a/drivers/block/aoe/aoe.h~aoe-ignore-vendor-extension-aoe-responses +++ a/drivers/block/aoe/aoe.h @@ -18,6 +18,7 @@ enum { AOECMD_ATA, AOECMD_CFG, + AOECMD_VEND_MIN = 0xf0, AOEFL_RSP = (1<<3), AOEFL_ERR = (1<<2), diff -puN drivers/block/aoe/aoenet.c~aoe-ignore-vendor-extension-aoe-responses drivers/block/aoe/aoenet.c --- a/drivers/block/aoe/aoenet.c~aoe-ignore-vendor-extension-aoe-responses +++ a/drivers/block/aoe/aoenet.c @@ -142,6 +142,8 @@ aoenet_rcv(struct sk_buff *skb, struct n aoecmd_cfg_rsp(skb); break; default: + if (h->cmd >= AOECMD_VEND_MIN) + break; /* don't complain about vendor commands */ printk(KERN_INFO "aoe: unknown cmd %d\n", h->cmd); } exit: _ Patches currently in -mm which might be from ecashin@xxxxxxxxxx are origin.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