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.] [PATCH v4] batman-adv: fix rare race conditions on interface removal
Date: Sat, 05 Nov 2016 12:25:46 +0100	[thread overview]
Message-ID: <6878609.IJnMAHbfGn@sven-edge> (raw)
In-Reply-To: <20161101084444.17429-1-linus.luessing@c0d3.blue>

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

On Dienstag, 1. November 2016 09:44:44 CET Linus Lüssing wrote:
[...]
> ---
> 
> Changes in v4:
> * rebased to master
> * tried to better explain the severity in the commit message
> * trimmed call trace in commit message
> * made code comments and the WARN_ONCE less funny, but more informative
> * reworded bm_list to cleanup_list
> * shortened batadv_forw_packet_steal() declaration in send.h
>   to avoid a faulty checkpatch warning.
> * removed unnecessary hlist_add_head() in batadv_forw_packet_steal()
> * changed hlist_del() to hlist_del_init() in batadv_forw_packet_steal()
>   -> to be able to reach WARN_ONCE instead of crashing upon calling
>      hlist_del()

Thanks for all the changes. Lets see if we finally got this one (please no
regression, please no regressions, ...) :)

Applied in 8a436b94d731873bd3d771aa146956420fbec458 [1].

Thanks,
	Sven

[1] https://git.open-mesh.org/batman-adv.git/commit/8a436b94d731873bd3d771aa146956420fbec458

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

      reply	other threads:[~2016-11-05 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-01  8:44 [B.A.T.M.A.N.] [PATCH v4] batman-adv: fix rare race conditions on interface removal Linus Lüssing
2016-11-05 11:25 ` 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=6878609.IJnMAHbfGn@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