All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: linux-bcachefs@vger.kernel.org
Cc: Kent Overstreet <kent.overstreet@linux.dev>
Subject: [PATCH 0/3] better error messages for ioctls
Date: Fri, 29 Aug 2025 02:54:04 -0400	[thread overview]
Message-ID: <20250829065409.3248746-1-kent.overstreet@linux.dev> (raw)

This fixes a common user complaint - uninformative error messages from
various bcachefs-tools commands.

Add v2 versions of various ioctls that include a 'struct
bch_ioctl_err_mesg', a pointer to a userspace buffer for an error
message - and plumb a printbuf through various code for returning
errors.

Kent Overstreet (3):
  bcachefs: Add v2 ioctls that return error strings
  bcachefs: v2 versions of subvolume ioctls
  bcachefs: Plumb error messages through data drop paths

 fs/bcachefs/bcachefs_ioctl.h |  87 ++++++++++++++-----
 fs/bcachefs/chardev.c        | 159 +++++++++++++++++++++++++++++++++--
 fs/bcachefs/chardev.h        |   3 +
 fs/bcachefs/ec.c             |  23 +++--
 fs/bcachefs/ec.h             |   5 +-
 fs/bcachefs/fs-ioctl.c       |  91 ++++++++++++++++++--
 fs/bcachefs/migrate.c        |  55 ++++++------
 fs/bcachefs/migrate.h        |   4 +-
 fs/bcachefs/super.c          |   6 +-
 9 files changed, 359 insertions(+), 74 deletions(-)

-- 
2.50.1


             reply	other threads:[~2025-08-29  6:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29  6:54 Kent Overstreet [this message]
2025-08-29  6:54 ` [PATCH 1/3] bcachefs: Add v2 ioctls that return error strings Kent Overstreet
2025-08-29  6:54 ` [PATCH 2/3] bcachefs: v2 versions of subvolume ioctls Kent Overstreet
2025-08-29  6:54 ` [PATCH 3/3] bcachefs: Plumb error messages through data drop paths Kent Overstreet

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=20250829065409.3248746-1-kent.overstreet@linux.dev \
    --to=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.