[3.7] subpath/atomic writer fixes

[liggitt]

Addresses CVE-2017-1002101, CVE-2017-1002102

[liggitt]

/retest

[mfojtik]

/retest
/lgtm

[mfojtik]

/retest

[jsafrane]

/lgtm
for the new commits

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, liggitt, mfojtik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• vendor/k8s.io/kubernetes/pkg/OWNERS [liggitt,mfojtik]
• vendor/k8s.io/kubernetes/test/OWNERS [liggitt,mfojtik]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jsafrane]

/retest

[openshift-ci-robot]

New changes are detected. LGTM label has been removed.

[smarterclayton]

/test gcp

[openshift-ci-robot]

@liggitt: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/openshift-jenkins/extended_conformance_install	6580d89	link	/test extended_conformance_install
ci/openshift-jenkins/end_to_end	6580d89	link	/test end_to_end
ci/openshift-jenkins/gcp	6580d89	link	/test gcp

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[liggitt]

CI failures are unrelated.

[liggitt]

@smarterclayton merged

[gh1001]

@liggitt are Origin clusters (with SELinux) that only allow users to run the restricted scc impacted by these?