From: Jeff Layton <jlayton@kernel.org> To: viro@ZenIV.linux.org.uk, dhowells@redhat.com Cc: willy@infradead.org, andres@anarazel.de, cmaiolino@redhat.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: [PATCH 5/5] samples: extend test-fsinfo to access error_state Date: Mon, 4 Jun 2018 14:03:04 -0400 [thread overview] Message-ID: <20180604180304.9662-6-jlayton@kernel.org> (raw) In-Reply-To: <20180604180304.9662-1-jlayton@kernel.org> From: Jeff Layton <jlayton@redhat.com> Add support for error_state struct to test-fsinfo sample program. Signed-off-by: Jeff Layton <jlayton@redhat.com> --- samples/statx/test-fsinfo.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/samples/statx/test-fsinfo.c b/samples/statx/test-fsinfo.c index 9d70c422da11..b383a6ec81a0 100644 --- a/samples/statx/test-fsinfo.c +++ b/samples/statx/test-fsinfo.c @@ -60,6 +60,7 @@ static const __u8 fsinfo_buffer_sizes[fsinfo_attr__nr] = { FSINFO_STRING (name_encoding), FSINFO_STRING (name_codepage), FSINFO_STRUCT (io_size), + FSINFO_STRUCT (error_state), }; #define FSINFO_NAME(N) [fsinfo_attr_##N] = #N @@ -84,6 +85,7 @@ static const char *fsinfo_attr_names[fsinfo_attr__nr] = { FSINFO_NAME(name_encoding), FSINFO_NAME(name_codepage), FSINFO_NAME(io_size), + FSINFO_NAME(error_state), }; union reply { @@ -98,6 +100,7 @@ union reply { struct fsinfo_volume_uuid uuid; struct fsinfo_server_address srv_addr; struct fsinfo_io_size io_size; + struct fsinfo_error_state error_state; }; static void dump_hex(unsigned int *data, int from, int to) @@ -303,6 +306,15 @@ static void dump_attr_io_size(union reply *r, int size) printf("bs=%u\n", f->block_size); } +static void dump_attr_error_state(union reply *r, int size) +{ + struct fsinfo_error_state *f = &r->error_state; + + printf("err_cookie=0x%x err_last=%u\n", + f->wb_error_cookie, + f->wb_error_last); +} + /* * */ @@ -320,6 +332,7 @@ static const dumper_t fsinfo_attr_dumper[fsinfo_attr__nr] = { FSINFO_DUMPER(volume_uuid), FSINFO_DUMPER(server_address), FSINFO_DUMPER(io_size), + FSINFO_DUMPER(error_state), }; static void dump_fsinfo(enum fsinfo_attribute attr, __u8 about, -- 2.17.0
prev parent reply other threads:[~2018-06-04 18:03 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-04 18:02 [PATCH 0/5] vfs: track per-sb writeback errors and report them via fsinfo() Jeff Layton 2018-06-04 18:03 ` [PATCH 1/5] vfs: track per-sb writeback errors Jeff Layton 2018-06-04 18:03 ` [PATCH 2/5] buffer: record blockdev write errors in super_block that backs them Jeff Layton 2018-06-06 15:56 ` Jeff Layton 2018-06-19 10:40 ` Jeff Layton 2018-06-19 13:03 ` Jeff Layton 2018-06-04 18:03 ` [PATCH 3/5] errseq: add a new errseq_scrape function Jeff Layton 2018-06-04 18:03 ` [PATCH 4/5] vfs: allow fsinfo to fetch the current state of s_wb_err Jeff Layton 2018-06-04 18:03 ` Jeff Layton [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=20180604180304.9662-6-jlayton@kernel.org \ --to=jlayton@kernel.org \ --cc=andres@anarazel.de \ --cc=cmaiolino@redhat.com \ --cc=dhowells@redhat.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=viro@ZenIV.linux.org.uk \ --cc=willy@infradead.org \ --subject='Re: [PATCH 5/5] samples: extend test-fsinfo to access error_state' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).