b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
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.] [PATCH v3 0/2] batman-adv: hard interface removal fixes
Date: Thu,  6 Oct 2016 01:43:06 +0200	[thread overview]
Message-ID: <20161005234308.29871-1-linus.luessing@c0d3.blue> (raw)

Hi,

This patchset contains another, revived patch (1/2). As we had quite
some trouble validating the patches back then in Aalborg, I tried to
push the overall structure in a hopefully easier to read and comprehend,
API like style. While keeping the initial idea (that is, steal and claim
forwarding packets from the queue under spinlock, then wait and free
without spinlock as a second step) intact.

The second patch is another kernel splat I came across while playing
with msleep(s)/mdelay()s in the purging routines.

Regards, Linus


PS: Especially for 1/2 I'm unsure whether to target it for maint/stable.
It didn't seem to be a show stopper for anyone within the last three years
(had been the only one reporting it at #168, I think?). And the fix is
difficult to do as one-liners, unless risking to introduce new race
conditions.


             reply	other threads:[~2016-10-05 23:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 23:43 Linus Lüssing [this message]
2016-10-05 23:43 ` [B.A.T.M.A.N.] [PATCH v3 1/2] batman-adv: fix race conditions on interface removal Linus Lüssing
2016-10-21 12:30   ` Sven Eckelmann
2016-10-29  2:46     ` Linus Lüssing
2016-10-29  6:55       ` Sven Eckelmann
2016-10-31  7:22         ` Linus Lüssing
2016-10-31  8:09           ` Sven Eckelmann
2016-10-31  9:57             ` Linus Lüssing
2016-10-05 23:43 ` [B.A.T.M.A.N.] [PATCH v3 2/2] batman-adv: fix splat on disabling an interface Linus Lüssing
2016-10-21 12:49   ` Sven Eckelmann

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=20161005234308.29871-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).