From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs: fix panic_mask documentation
Date: Thu, 5 Feb 2015 09:08:29 -0500 [thread overview]
Message-ID: <20150205140829.GA31625@laptop.bfoster> (raw)
In-Reply-To: <54D0F858.5010804@redhat.com>
On Tue, Feb 03, 2015 at 10:33:28AM -0600, Eric Sandeen wrote:
> This bit of the docs didn't quite reflect reality.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> diff --git a/Documentation/filesystems/xfs.txt b/Documentation/filesystems/xfs.txt
> index 5be51fd..157d440 100644
> --- a/Documentation/filesystems/xfs.txt
> +++ b/Documentation/filesystems/xfs.txt
> @@ -287,7 +287,7 @@ The following sysctls are available for the XFS filesystem:
> XFS_ERRLEVEL_LOW: 1
> XFS_ERRLEVEL_HIGH: 5
>
> - fs.xfs.panic_mask (Min: 0 Default: 0 Max: 127)
> + fs.xfs.panic_mask (Min: 0 Default: 0 Max: 255)
> Causes certain error conditions to call BUG(). Value is a bitmask;
> AND together the tags which represent errors which should cause panics:
Looks good, though shouldn't the above say "OR together the tags ..?"
Brian
>
> @@ -299,6 +299,7 @@ The following sysctls are available for the XFS filesystem:
> XFS_PTAG_SHUTDOWN_CORRUPT 0x00000010
> XFS_PTAG_SHUTDOWN_IOERROR 0x00000020
> XFS_PTAG_SHUTDOWN_LOGERROR 0x00000040
> + XFS_PTAG_FSBLOCK_ZERO 0x00000080
>
> This option is intended for debugging only.
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-02-05 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 16:33 [PATCH] xfs: fix panic_mask documentation Eric Sandeen
2015-02-05 14:08 ` Brian Foster [this message]
2015-02-05 16:44 ` [PATCH V2] " Eric Sandeen
2015-02-05 22:05 ` Brian Foster
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=20150205140829.GA31625@laptop.bfoster \
--to=bfoster@redhat.com \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.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