On 26 April 2017 at 19:03, Arend Van Spriel <arend.vanspriel@xxxxxxxxxxxx> wrote: > > > On 26-4-2017 17:44, Steve deRosier wrote: >> On Wed, Apr 26, 2017 at 1:53 AM, Kalle Valo <kvalo@xxxxxxxxxxxxxx> wrote: >>> Arend Van Spriel <arend.vanspriel@xxxxxxxxxxxx> wrote: >>>> An issue was found brcmfmac driver in which a skbuff in .start_xmit() >>>> callback was actually cloned. So instead of checking for sufficient >>>> headroom it should also be writable. Hence use skb_cow_head() to >>>> check and expand the headroom appropriately. >>>> >>>> Signed-off-by: Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx> >>> >>> Steve, would you have time to run a quick test with this? >>> >>> Patch set to Deferred. >>> >> >> Happy to give it a quick spin on both of my platforms. >> >> @Arend: is there some demonstrable before/after that shows a problem I >> can detect at runtime? I understand your thought about putting a >> skb_clone() in there, but what are the expectations? And is any >> problem evident without explicitly modding the code with the clone? > > Ok. So the root cause is explained in a email to netdev mailing list, > but I can not find it. The sender was probably not a member. I will > forward that email to you and cc: linux-wireless. Basically, you need to > setup a bridge and run hostapd in bridged mode. Incoming multicast > traffic will be cloned by bridge and sent all interfaces in the bridge. > If more than one driver puts additional payload in the headroom they are > basically mucking about in the same buffer space so packets probably > never end up in the devices. In case of ath6kl the patch is in area > where driver/device determines IP checksum if it is supported (if I am > not mistaken). So not sure how easy it is to replicate without patching > it for testing. > > Regards, > Arend That was me. The full mechanism can be seen on the Raspberry Pi github issue tracker here https://github.com/raspberrypi/firmware/issues/673 In brief, when bridging between two devices, if both devices fail to 'unclone' then header corruption could occur if both the devices made header changes since they are both looking at the same data. The Pi has a smsc9x ethernet device and the Brcm Wireless chip - both had the fault, so we were getting corrupted headers, and eventual failure of ethernet. The same fault appears in a large subset of drivers in my brief examinations. James
