From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] proc01: Add /proc/dirty/dirty_list to known_issues
Date: Wed, 12 May 2021 17:31:57 +0200 [thread overview]
Message-ID: <YJv07fCsOlCR0LZH@pevik> (raw)
In-Reply-To: <20210308033428.20924-1-zhaogongyi@huawei.com>
Hi Zhao,
> When we open the file /proc/dirty/dirty_list directly, it will return -1 and
> set the errno to ENOMEM.
...
> +++ b/testcases/kernel/fs/proc/proc01.c
> @@ -85,6 +85,7 @@ static const struct mapping known_issues[] = {
> {"open", "/proc/sal/init/data", EBUSY},
> {"open", "/proc/sal/mca/data", EBUSY},
> {"open", "/proc/fs/nfsd/pool_stats", ENODEV},
> + {"open", "/proc/dirty/dirty_list", ENOMEM},
Is /proc/dirty/dirty_list in mainline? We haven't found "dirty_list" string in
mainline git (there is dirty_list code, but not "dirty_list" string).
I'd prefer not to add vendor specific files, or at least to document them.
Kind regards,
Petr
prev parent reply other threads:[~2021-05-12 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 3:34 [LTP] [PATCH] proc01: Add /proc/dirty/dirty_list to known_issues Zhao Gongyi
2021-05-12 15:31 ` Petr Vorel [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=YJv07fCsOlCR0LZH@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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