From: Akinobu Mita <akinobu.mita@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v2] fault-inject: support systematic fault injection
Date: Tue, 4 Apr 2017 23:57:31 +0900 [thread overview]
Message-ID: <CAC5umyggX4OLBSG5z0gLZ3Tc0=ev_DrcgbRbKnw9i=uzXTSsUg@mail.gmail.com> (raw)
In-Reply-To: <20170328130128.101773-1-dvyukov@google.com>
2017-03-28 22:01 GMT+09:00 Dmitry Vyukov <dvyukov@google.com>:
> diff --git a/fs/proc/base.c b/fs/proc/base.c
> index 6e8655845830..66001172249b 100644
> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -1353,6 +1353,53 @@ static const struct file_operations proc_fault_inject_operations = {
> .write = proc_fault_inject_write,
> .llseek = generic_file_llseek,
> };
> +
> +static ssize_t proc_fail_nth_write(struct file *file, const char __user *buf,
> + size_t count, loff_t *ppos)
> +{
> + struct task_struct *task;
> + int err, n;
> +
> + task = get_proc_task(file_inode(file));
> + if (!task)
> + return -ESRCH;
> + put_task_struct(task);
> + if (task != current)
> + return -EPERM;
> + err = kstrtoint_from_user(buf, count, 10, &n);
> + if (err)
> + return err;
> + if (n < 0 || n == INT_MAX)
> + return -EINVAL;
> + current->fail_nth = n + 1;
> + return len;
> +}
> +
> +static ssize_t proc_fail_nth_read(struct file *file, char __user *buf,
> + size_t count, loff_t *ppos)
> +{
> + struct task_struct *task;
> + int err;
> +
> + task = get_proc_task(file_inode(file));
> + if (!task)
> + return -ESRCH;
> + put_task_struct(task);
> + if (task != current)
> + return -EPERM;
> + if (count < 1)
> + return -EINVAL;
> + err = put_user((char)(current->fail_nth ? 'N' : 'Y'), buf);
> + if (err)
> + return err;
> + current->fail_nth = 0;
> + return 1;
> +}
> +
> +static const struct file_operations proc_fail_nth_operations = {
> + .read = proc_fail_nth_read,
> + .write = proc_fail_nth_write,
> +};
> #endif
>
>
> @@ -3296,6 +3343,11 @@ static const struct pid_entry tid_base_stuff[] = {
> #endif
> #ifdef CONFIG_FAULT_INJECTION
> REG("make-it-fail", S_IRUGO|S_IWUSR, proc_fault_inject_operations),
> + /*
> + * Operations on the file check that the task is current,
> + * so we create it with 0666 to support testing under unprivileged user.
> + */
> + REG("fail-nth", 0666, proc_fail_nth_operations),
> #endif
This file is owned by the currnet user. So we can create it with 0644
and just allow unprivileged user to write it. And it enables to remove
the check that the task is current or not in read/write operations.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-04-04 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 13:01 Dmitry Vyukov
2017-03-28 21:40 ` Andrew Morton
2017-03-28 23:41 ` Akinobu Mita
2017-03-30 23:04 ` Andrew Morton
2017-04-04 14:57 ` Akinobu Mita [this message]
2017-04-06 18:33 ` Michal Hocko
2017-04-07 16:47 ` Akinobu Mita
2017-04-08 17:40 ` Dmitry Vyukov
2017-04-09 10:39 ` Akinobu Mita
2017-05-24 10:22 ` Dmitry Vyukov
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='CAC5umyggX4OLBSG5z0gLZ3Tc0=ev_DrcgbRbKnw9i=uzXTSsUg@mail.gmail.com' \
--to=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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