b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCH 0/3] batctl: Add netlink support for sysfs-only functionality
Date: Wed,  3 Apr 2019 20:01:16 +0200	[thread overview]
Message-ID: <20190403180119.26800-1-sven@narfation.org> (raw)

Hi,

some functionality in batctl was previously using sysfs to implement some
of its features. Since the sysfs support can now be disabled in the kernel,
these features were broken in such setups. This was especially problematic
for functionality which depends on the main mesh interface. The check to
make sure that this is interface is a valid batadv interface were
exclusively using sysfs.

Switching them to (or actually extending them to support) netlink should
fix this. The old sysfs functionality is still here but can be removed in
the future.

Kind regards,
	Sven

Sven Eckelmann (3):
  batctl: Support checking of meshif without sysfs
  batctl: Reimplement VLAN translation using helper
  batctl: Add netlink fallback for sysfs' iface_status

 debug.c     |   2 +-
 functions.c | 407 ++++++++++++++++++++++++++++++----------------------
 functions.h |   2 +-
 interface.c |  92 +++++++++++-
 4 files changed, 331 insertions(+), 172 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-04-03 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 18:01 Sven Eckelmann [this message]
2019-04-03 18:01 ` [B.A.T.M.A.N.] [PATCH 1/3] batctl: Support checking of meshif without sysfs Sven Eckelmann
2019-04-03 18:01 ` [B.A.T.M.A.N.] [PATCH 2/3] batctl: Reimplement VLAN translation using helper Sven Eckelmann
2019-04-03 18:01 ` [B.A.T.M.A.N.] [PATCH 3/3] batctl: Add netlink fallback for sysfs' iface_status 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=20190403180119.26800-1-sven@narfation.org \
    --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;
as well as URLs for NNTP newsgroup(s).