From owner-freebsd-bugs@FreeBSD.ORG Fri Apr 20 15:30:12 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA46C106567C for ; Fri, 20 Apr 2012 15:30:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C4FD88FC20 for ; Fri, 20 Apr 2012 15:30:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3KFUCYP002871 for ; Fri, 20 Apr 2012 15:30:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3KFUCUp002868; Fri, 20 Apr 2012 15:30:12 GMT (envelope-from gnats) Date: Fri, 20 Apr 2012 15:30:12 GMT Message-Id: <201204201530.q3KFUCUp002868@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Andreas Longwitz Cc: Subject: Re: kern/155658: [amr] [patch] amr_ioctl(): call of malloc() causes memory corruption and panic X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andreas Longwitz List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2012 15:30:12 -0000 The following reply was made to PR kern/155658; it has been noted by GNATS. From: Andreas Longwitz To: Scott Long Cc: bug-followup@freebsd.org, John Baldwin Subject: Re: kern/155658: [amr] [patch] amr_ioctl(): call of malloc() causes memory corruption and panic Date: Fri, 20 Apr 2012 17:20:53 +0200 > Worst firmware ever. Seriously. Agree, but I run three dozen servers with amr controllers of four different types and all behave equal. Without source and/or docs I can not decide what is firmware and/or megarc error. I must live with this situation and I am happy, that this is the only corner in my FreeBSD world that is not "open". >> Ah, ok. I think we should just make the minimum buffer size 32k which >> should workaround this. I've updated the patch at the same URL: >> >> http://www.freebsd.org/~jhb/patches/amr_buffer_len.patch >> >> -- >> John Baldwin I have tested the updated patch, for me it is ok. Thanks you all for investigating in this problem. Andreas Longwitz