From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Getting better/supplementary error info back to userspace
Date: Fri, 21 Jul 2017 14:41:39 +0100 [thread overview]
Message-ID: <7884.1500644499@warthog.procyon.org.uk> (raw)
In-Reply-To: <CA+55aFySG7NAvsphb76J-M2YuM8_4wQ8Cvufu24Gb=EhpaoKTg@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> But every time it comes up people ignore this basic issue:
>
> [torvalds@i7 linux]$ git grep -e '-E[A-Z]\{4\}' | wc -l
> 182523
>
>
> Give it up. It's really is a horrible idea for so many reasons.
Are you okay with me making it possible to retrieve mount errors, warnings and
informational messages through fd-arbitrated-mount I'm working on? For
example (and skipping some of the parameters for brevity):
int fs_fd;
static inline void e(int x)
{
char buf[1024];
int i;
if (x == -1)
fprintf(stderr, "Mount error: %m\n");
/* Read back any messages */
while (i = read(fs_fd, buf), i != -1) {
buf[i] = 0;
fprintf(stderr, "%s\n", buf);
}
if (x == -1)
exit(1);
}
fs_fd = fsopen("ext4");
e(write(fs_fd, "d /dev/sda3"));
e(write(fs_fd, "o user_xattr"));
e(write(fs_fd, "o acl"));
e(write(fs_fd, "o data=ordered"));
e(write(fs_fd, "x create"));
e(fsmount(fs_fd, AT_FDCWD, "/mnt", MS_NODEV));
close(fs_fd);
David
prev parent reply other threads:[~2017-07-21 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 12:43 David Howells
2017-07-12 14:33 ` Arnaldo Carvalho de Melo
2017-07-12 14:44 ` Arnaldo Carvalho de Melo
2017-07-12 14:57 ` David Howells
2017-07-12 15:21 ` Stephen Hemminger
2017-07-12 16:19 ` Linus Torvalds
2017-07-12 16:35 ` Stephen Hemminger
2017-07-19 13:02 ` Steven Rostedt
2017-07-24 7:55 ` Miklos Szeredi
2017-07-24 8:25 ` David Howells
2017-07-21 13:41 ` David Howells [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=7884.1500644499@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox