public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH v5 1/4] Revert "batman-adv: Fix hardif remove/add race"
Date: Mon, 20 Jun 2016 16:36:23 +0800	[thread overview]
Message-ID: <5728038.Z0THFbVVB6@voltaire> (raw)
In-Reply-To: <1465796492-5039-1-git-send-email-sven@narfation.org>

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

On Monday, June 13, 2016 07:41:29 Sven Eckelmann wrote:
> The description given in the commit is misleading and is at least not true
> for sysfs. The sysfs file structure should instead be deleted immediately on
> rtnl notifications and be underlying objects should be removed later when
> all kobject_put were done for the object.
> 
> This reverts commit 6b0485c758be ("batman-adv: Fix hardif remove/add race")

Applied in revision b58db7b.

@Andrew: Sven's patchset aims to fix the problem you encountered in a better 
way while also addressing other issues. Can you give it a try in your 
environment to confirm it fixes your problem too ?

Thanks,
Marek

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

      parent reply	other threads:[~2016-06-20  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  5:41 [B.A.T.M.A.N.] [PATCH v5 1/4] Revert "batman-adv: Fix hardif remove/add race" Sven Eckelmann
2016-06-13  5:41 ` [B.A.T.M.A.N.] [PATCH v5 2/4] batman-adv: Modify mesh_iface outside sysfs context Sven Eckelmann
2016-06-20  8:36   ` Marek Lindner
2016-06-13  5:41 ` [B.A.T.M.A.N.] [PATCH v5 3/4] batman-adv: Revert "postpone sysfs removal when unregistering" Sven Eckelmann
2016-06-20  8:37   ` Marek Lindner
2016-06-13  5:41 ` [B.A.T.M.A.N.] [PATCH v5 4/4] batman-adv: Avoid sysfs name collision for netns moves Sven Eckelmann
2016-06-20  8:37   ` Marek Lindner
2016-06-20  8:36 ` Marek Lindner [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=5728038.Z0THFbVVB6@voltaire \
    --to=mareklindner@neomailbox.ch \
    --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