From: Richard Weinberger <richard@nod.at>
To: schaecsn <schaecsn@gmx.net>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stefan Schaeckeler <sschaeck@cisco.com>
Subject: Re: [PATCH v3] ubifs: ubifs to export filesystem error counters
Date: Thu, 28 Oct 2021 09:16:16 +0200 (CEST) [thread overview]
Message-ID: <791707806.43634.1635405376333.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20211028062124.12539-1-schaecsn@gmx.net>
Stefan,
----- Ursprüngliche Mail -----
> Von: "schaecsn" <schaecsn@gmx.net>
> An: "richard" <richard@nod.at>, "linux-mtd" <linux-mtd@lists.infradead.org>, "linux-kernel"
> <linux-kernel@vger.kernel.org>
> CC: "Stefan Schaeckeler" <sschaeck@cisco.com>
> Gesendet: Donnerstag, 28. Oktober 2021 08:21:24
> Betreff: [PATCH v3] ubifs: ubifs to export filesystem error counters
> From: Stefan Schaeckeler <sschaeck@cisco.com>
>
> 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 v3:
> - Added Documentation/ABI/testing/sysfs-fs-ubifs
> - Added Documentation/ABI/testing/sysfs-fs-ubifs to MAINTAINERS
I asked for just the Documentation. v2 of your patch is already in linux-next. :-)
Thanks,
//richard
prev parent reply other threads:[~2021-10-28 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 6:21 [PATCH v3] ubifs: ubifs to export filesystem error counters Stefan Schaeckeler
2021-10-28 7:16 ` Richard Weinberger [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=791707806.43634.1635405376333.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=schaecsn@gmx.net \
--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