B.A.T.M.A.N Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Sven Eckelmann <sven@narfation.org>
Subject: [PATCH 0/4] alfred: client: random fixes
Date: Fri, 31 Jul 2026 09:40:12 +0200	[thread overview]
Message-ID: <20260731-bugfixes-client-v1-0-83d8c7a26421@narfation.org> (raw)

Similar to the batctl fixes, I have now compiled a list of potential fixes
for alfred. Instead of posting everything at once, I will be posted in
smaller chunks. They are just various (mostly minor) problems which should
be tackled at some point.

Signed-off-by: Sven Eckelmann <sven@narfation.org>
---
Sven Eckelmann (4):
      alfred: fix error code from unix_sock_req_data_reply
      alfred: avoid endless-loop when reading data from stdin fails
      alfred: close the listening socket on daemon setup errors
      alfred: handle short reads when waiting for daemon answer

 alfred.h    |  1 +
 client.c    | 77 +++++++++++++++++++++++++++++++++++++++----------------------
 unix_sock.c | 39 +++++++++++++++++--------------
 util.c      | 25 ++++++++++++++++++++
 4 files changed, 97 insertions(+), 45 deletions(-)
---
base-commit: 462a0cf40615f62e0912c36d72a75accbb26f5ee
change-id: 20260731-bugfixes-client-0d5ed91e75db

Best regards,
--  
Sven Eckelmann <sven@narfation.org>


             reply	other threads:[~2026-07-31  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  7:40 Sven Eckelmann [this message]
2026-07-31  7:40 ` [PATCH 1/4] alfred: fix error code from unix_sock_req_data_reply Sven Eckelmann
2026-07-31  7:40 ` [PATCH 2/4] alfred: avoid endless-loop when reading data from stdin fails Sven Eckelmann
2026-07-31  7:40 ` [PATCH 3/4] alfred: close the listening socket on daemon setup errors Sven Eckelmann
2026-07-31  7:40 ` [PATCH 4/4] alfred: handle short reads when waiting for daemon answer 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=20260731-bugfixes-client-v1-0-83d8c7a26421@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