From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] Test for memfd_create() syscall withMFD_HUGETLBflag.
Date: Tue, 31 Jul 2018 06:14:29 -0400 (EDT) [thread overview]
Message-ID: <554879696.37043235.1533032069506.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <4504bc463448837a2489d78d43a19f49.squirrel@pike.zilogic.com>
----- Original Message -----
>
> Hi,
>
> Thanks for your code review. We will make the changes in next patch.
>
> In set-up(), we are using SAFE_FILE_LINES_SCANF(). Do we need to go
> for FILE_LINES_SCANF() with tst_brk-> TCONF on error?
I don't have strong opinion either way. You can do that - the only
way I see it failing now is if /proc was not mounted, which seems unlikely.
Regards,
Jan
>
> Regards,
> Vishnu K
>
>
next prev parent reply other threads:[~2018-07-31 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 13:53 [LTP] [PATCH v3] Test for memfd_create() syscall with MFD_HUGETLB flag Vishnu K
2018-07-30 14:10 ` Jan Stancek
2018-07-31 9:27 ` [LTP] [PATCH v3] Test for memfd_create() syscall withMFD_HUGETLBflag vishnu
2018-07-31 10:14 ` Jan Stancek [this message]
2018-07-31 13:11 ` [LTP] [PATCH v3] Test for memfd_create()syscallwithMFD_HUGETLBflag vishnu
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=554879696.37043235.1533032069506.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--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