mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Schaeckeler <schaecsn@gmx.net>
To: richard@nod.at
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	sschaeck@cisco.com
Subject: Re: [PATCH v2] ubifs: ubifs to export filesystem error counters
Date: Fri, 12 Nov 2021 18:13:30 -0800 (PST)	[thread overview]
Message-ID: <20211113021330.3CA4527F135@corona.crabdance.com> (raw)
In-Reply-To: <2065858791.38760.1635277003599.JavaMail.zimbra@nod.at> (message from Richard Weinberger on Tue, 26 Oct 2021 21:36:43 +0200 (CEST))

Hello Richard,

> > Not all ubifs filesystem errors are propagated to userspace.
> >
> > Export bad magic, bad node and crc errors via sysfs. This allows userspace
> > to notice filesystem errors:
> >
> > /sys/fs/ubifs/ubiX_Y/errors_magic
> > /sys/fs/ubifs/ubiX_Y/errors_node
> > /sys/fs/ubifs/ubiX_Y/errors_crc
> >
> > The counters are reset to 0 with a remount.
> >
> > Signed-off-by: Stefan Schaeckeler <sschaeck@cisco.com>
> > ---
> > Changes in v2:
> >  - merged sysfs.h header into ubifs.h.
> >  - io.c: wrapped incrementing error counters into new functions
> >    record_*_error().
> >  - sysfs.c: removed sysfs write callback for clearing stats.
> >  - sysfs.c: ubifs_sysfs_register(): free c->stats on error.
> >  - sysfs.c: ubifs_attr_show(): use sysfs_emit().
> >
> > fs/ubifs/Makefile |   2 +-
> > fs/ubifs/io.c     |  21 +++++++
> > fs/ubifs/super.c  |  16 ++++-
> > fs/ubifs/sysfs.c  | 153 ++++++++++++++++++++++++++++++++++++++++++++++
> > fs/ubifs/ubifs.h  |  35 +++++++++++
> > 5 files changed, 225 insertions(+), 2 deletions(-)
> > create mode 100644 fs/ubifs/sysfs.c
>
> Queued for 5.16.

The merge window for 5.16 is about to close. May I point out that, as far as I
can tell, you have not sent a pull request for ubifs, yet.

 Stefan

      reply	other threads:[~2021-11-13  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10  4:22 Stefan Schaeckeler
2021-10-26 19:36 ` Richard Weinberger
2021-11-13  2:13   ` Stefan Schaeckeler [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=20211113021330.3CA4527F135@corona.crabdance.com \
    --to=schaecsn@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=sschaeck@cisco.com \
    /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

all inboxes | Powered by JetHome®