From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCHv3 maint 0/5] Fixes for parallel OGM processing
Date: Tue, 16 Jun 2015 15:17:18 +0200 [thread overview]
Message-ID: <1434460643-3681-1-git-send-email-linus.luessing@c0d3.blue> (raw)
Hi,
Here are five fixes which address potential problems with parallel OGM
processing. For the multicast subsystem the issues can be quite severe
as found and pointed out by Sven here [0].
Cheers, Linus
[0]: https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2015-June/013193.html
-----
Changelog v3:
* [PATCHv3 maint 5/5]:
* added kerneldoc for new mcast_handler_lock in types.h
Changelog v2:
* Split [PATCH maint 1/2] into [PATCHv2 {1,2,3,4}/5]
* [PATCHv2 maint 5/5]:
* moved mcast_flags initialization outside of spinlock
* added spinlock in batadv_mcast_purge_orig()
(not strictly necessary bc. if we are here then the orig-node is
out-of-scope as it's going to be kfree'd a few instructions later
- but added for style reasons / to avoid future errors)
* added hlist_unhashed()+BUG() calls
(again, shouldn't be necessary as the checks and new spinlock should
avoid this case. But since the safety of hlist_del_rcu() isn't
directly obvious, better adding these annotations and to avoid
future regressions with kernel panics)
PS: Thanks to Marek for the suggestions.
next reply other threads:[~2015-06-16 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 13:17 Linus Lüssing [this message]
2015-06-16 13:17 ` [B.A.T.M.A.N.] [PATCHv3 maint 1/5] batman-adv: Make DAT capability changes atomic Linus Lüssing
2015-06-16 13:17 ` [B.A.T.M.A.N.] [PATCHv3 maint 2/5] batman-adv: Make NC " Linus Lüssing
2015-06-16 13:17 ` [B.A.T.M.A.N.] [PATCHv3 maint 3/5] batman-adv: Make TT " Linus Lüssing
2015-06-16 13:17 ` [B.A.T.M.A.N.] [PATCHv3 maint 4/5] batman-adv: Make MCAST " Linus Lüssing
2015-06-16 13:17 ` [B.A.T.M.A.N.] [PATCHv3 maint 5/5] batman-adv: Fix potential synchronization issues in mcast tvlv handler Linus Lüssing
2015-06-16 14:12 ` Marek Lindner
2015-06-16 14:38 ` Marek Lindner
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=1434460643-3681-1-git-send-email-linus.luessing@c0d3.blue \
--to=linus.luessing@c0d3.blue \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.