From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxlounge.net; s=mail; t=1562057182; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:openpgp:openpgp:autocrypt:autocrypt; bh=HcrU3xHf2es9K1eWmG8nbhDoxCTyXkGXB9fNsN37JPM=; b=cpOxtmSaP4trU3ozqBS66YZqBZWhUwjWDFuCuUs9XDb55dKzLjizVEO9O2JeTgOhFskerw IinNen6G4pMYKhk0XtE6GbHHBvu2IBjIMPTPZLmOUfLO8qc7svfe4VJhoL6uiyxZc4Aa3u EOuyYNmZ3JRSgRJrPNuAVkqg4TXOJUo= References: <41ac3aa3-cbf7-1b7b-d847-1fb308334931@linuxlounge.net> <21ab085f-0f7f-88bc-b661-af74dd9eeea2@linuxlounge.net> <3fcf8b05-e1ad-ac97-10bf-bd2b6354424c@linuxlounge.net> <908e9e90-70cc-7bbe-f83f-0810c9ef3925@cumulusnetworks.com> <5e43ba82-de32-e419-efc3-5dfca8291973@linuxlounge.net> <6dc6e89b-8b40-7dac-ec69-f4223d5dc147@cumulusnetworks.com> From: Martin Weinelt Message-ID: Date: Tue, 2 Jul 2019 10:46:22 +0200 In-Reply-To: <6dc6e89b-8b40-7dac-ec69-f4223d5dc147@cumulusnetworks.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [Bridge] Use-after-free in br_multicast_rcv List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikolay Aleksandrov , bridge@lists.linux-foundation.org, Roopa Prabhu Cc: netdev@vger.kernel.org Hi Nik, On 7/2/19 12:37 AM, Nikolay Aleksandrov wrote: > On 7/2/19 1:17 AM, Martin Weinelt wrote: >> Hi again, >> >> On 7/1/19 7:37 PM, Nikolay Aleksandrov wrote: >>> I see, thanks for clarifying this. So on the KASAN could you please try the attached patch ? >>> Also could you please run the br_multicast_rcv+xxx addresses through >>> linux/scripts/faddr2line for your kernel/bridge: >>> usage: faddr2line [--list] ... >>> >>> Thanks, >>> Nik >>> >> >> back with a new report. This is 5.2.0-rc7 + your patch. >> >> Best, >> Martin >> > > Thanks! Aaargh.. I made a stupid mistake hurrying to send the patch, apologies. > Here's the fixed version, please give it a go. This report is because > of my change, not because of the previous bug that should've been fixed. > I applied your latest patch against 5.2.0-rc7 and it seems to have fixed the issue as, after 6 hours of uptime, the KASAN report isn't coming up anymore. Also there are currently no kmemleak results coming up on 5.2.0-rc7, so I'll be looking at the v4.19.x series next. Thank you! Best Martin