[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eacdc1fe-df5c-472f-9e83-971bbe36e8b5@embeddedor.com>
Date: Mon, 8 Jan 2024 11:38:41 -0600
From: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>,
Dan Carpenter <dan.carpenter@...aro.org>
Cc: linux-hardening@...r.kernel.org, keescook@...omium.org,
error27@...il.com, gustavoars@...nel.org, Bryan Tan <bryantan@...are.com>,
Vishnu Dasa <vdasa@...are.com>,
VMware PV-Drivers Reviewers <pv-drivers@...are.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, vegard.nossum@...cle.com,
darren.kenny@...cle.com, syzkaller <syzkaller@...glegroups.com>
Subject: Re: [PATCH v2 2/2] VMCI: Fix memcpy() run-time warning in
dg_dispatch_as_host()
On 1/8/24 11:31, Harshit Mogalapalli wrote:
>> BTW, is this _warning_ really causing a crash?
>>
>
> I think we can say this can cause a crash in a way, WARN_ONCE() is still a WARNING and we can have systems with panic_on_warn set.
>
Oh yes! thanks for the clarification. :)
--
Gustavo
Powered by blists - more mailing lists