public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Invalid memory access during if add/del with multiple interfaces
Date: Sun, 29 Nov 2015 02:17:59 +0100	[thread overview]
Message-ID: <1696819.DY2yIRgCKv@sven-edge> (raw)
In-Reply-To: <29580650.TaMGDDyOBU@sven-edge>

[-- Attachment #1: Type: text/plain, Size: 839 bytes --]

On Sunday 29 November 2015 01:37:21 Sven Eckelmann wrote:
> [...]
> 
>     ==================================================================
>     BUG: KASAN: slab-out-of-bounds in
> batadv_iv_ogm_slide_own_bcast_window+0x298/0x376 [batman_adv] at addr fff
> 
>     Write of size 1 by task kworker/u4:2/67

The reads seem to be solved by the patch [1] which I've sent to the mailing 
list. But this write looks more interesting. The problem seems to be the 
missing locking for if_num + bat_iv.bcast_own/bat_iv.bcast_own_sum (with 
bat_iv.ogm_cnt_lock ?) in (or around) 
batadv_orig_hash_add_if/batadv_orig_hash_del_if.

And I don't know right now what causes the GPF but it can be reproduced (just 
takes some time until it happens).

Kind regards,
	Sven


[1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2015-November/013836.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-11-29  1:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-29  0:37 [B.A.T.M.A.N.] Invalid memory access during if add/del with multiple interfaces Sven Eckelmann
2015-11-29  1:17 ` Sven Eckelmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1696819.DY2yIRgCKv@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox