From: chrubis@suse.cz
To: Matus Marhefka <mmarhefk@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 2/2 v2] containers: added mountns/mountns04.c
Date: Wed, 24 Sep 2014 10:14:20 +0200 [thread overview]
Message-ID: <20140924081420.GC10825@rei> (raw)
In-Reply-To: <1409320025-12778-1-git-send-email-mmarhefk@redhat.com>
Hi!
> +static void setup(void)
> +{
> + tst_require_root(NULL);
> + check_newns(); /* from mountns_helper.h */
Please remove this comment.
> + tst_tmpdir();
> + SAFE_MKDIR(cleanup, DIRA, 0777);
> + SAFE_MKDIR(cleanup, DIRB, 0777);
> + SAFE_TOUCH(cleanup, DIRA"/A", 0, NULL);
> + SAFE_TOUCH(cleanup, DIRB"/B", 0, NULL);
> +}
> +
> +static void test(void)
> +{
> + /* unshares the mount ns */
> + if (unshare(CLONE_NEWNS) == -1)
> + tst_brkm(TBROK | TERRNO, cleanup, "unshare failed");
> + /* makes sure mounts/umounts have no effect on a real system */
> + SAFE_MOUNT(cleanup, "none", "/", "none", MS_REC|MS_PRIVATE, NULL);
> +
> + /* bind mounts DIRA to itself */
> + SAFE_MOUNT(cleanup, DIRA, DIRA, "none", MS_BIND, NULL);
> + /* bind mounts DIRB to itself */
> + SAFE_MOUNT(cleanup, DIRB, DIRB, "none", MS_BIND, NULL);
> +
> + /* makes mount DIRA unbindable */
> + SAFE_MOUNT(cleanup, "none", DIRA, "none", MS_UNBINDABLE, NULL);
> + /* makes mount DIRB shared */
> + SAFE_MOUNT(cleanup, "none", DIRB, "none", MS_SHARED, NULL);
> +
> + /* tries to bind mount unbindable DIRA to DIRB which should fail */
> + if (mount(DIRA, DIRB, "none", MS_BIND, NULL) == -1)
> + tst_resm(TPASS, "unbindable mount passed");
> + else {
> + SAFE_UMOUNT(cleanup, DIRB);
> + tst_resm(TFAIL, "unbindable mount faled");
> + }
This is merely cosmetic, but LKML coding style preffers having curly
brackets on both branches if they needs to be over one of them.
> +#else /* MS_SHARED && MS_PRIVATE && MS_REC && MS_UNBINDABLE */
And the comment about ifdefs applies here as well.
Otherwise it looks good.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-09-24 8:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 9:59 [LTP] [PATCH 1/2] containers: added mountns/mountns03.c Matus Marhefka
2014-08-26 9:59 ` [LTP] [PATCH 2/2] containers: added mountns/mountns04.c Matus Marhefka
2014-08-29 13:47 ` [LTP] [PATCH 2/2 v2] " Matus Marhefka
2014-09-04 14:21 ` Jan Stancek
2014-10-02 13:47 ` Cyril Hrubis
[not found] ` <1080778288.46330076.1412258911538.JavaMail.zimbra@redhat.com>
2014-10-15 12:39 ` Cyril Hrubis
2014-09-24 8:14 ` chrubis [this message]
2014-10-02 12:29 ` [LTP] [PATCH 2/2 v3] " Matus Marhefka
2014-08-29 13:46 ` [LTP] [PATCH 1/2 v2] containers: added mountns/mountns03.c Matus Marhefka
2014-09-04 14:13 ` Jan Stancek
2014-09-11 15:09 ` Jiri Jaburek
2014-09-12 12:59 ` Jan Stancek
2014-09-12 13:41 ` Jiri Jaburek
2014-09-12 14:19 ` Jan Stancek
2014-09-24 7:56 ` chrubis
[not found] ` <273164774.30346037.1411649870605.JavaMail.zimbra@redhat.com>
[not found] ` <461070711.43439951.1411650253035.JavaMail.zimbra@redhat.com>
2014-09-29 8:14 ` chrubis
2014-10-02 12:28 ` [LTP] [PATCH 1/2 v3] " Matus Marhefka
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=20140924081420.GC10825@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=mmarhefk@redhat.com \
/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