Revert "net: fix some sparse errors"
Revert "smdk4412: network: squashed commits"
Revert "Handle 'sk' being NULL in UID-based routing."
Revert "net: core: Support UID-based routing."
Revert "net: ipv6: Add IPv6 support to the ping socket."
Revert "ipv4: tcp: fix TOS value in ACK messages sent from TIME_WAIT"
Revert "ipv4: use a 64bit load/store in output path"
Revert "ipv4: route non-local sources for raw socket"
Selinux: Remove related code for Samsung's "CONFIG_ALWAYS_ENFORCE"
selinux: fix inode security list corruption

sb_finish_set_opts() can race with inode_free_security()
when initializing inode security structures for inodes
created prior to initial policy load or by the filesystem
during ->mount().   This appears to have always been
a possible race, but commit 3dc91d4 ("SELinux:  Fix possible
NULL pointer dereference in selinux_inode_permission()")
made it more evident by immediately reusing the unioned
list/rcu element  of the inode security structure for call_rcu()
upon an inode_free_security().  But the underlying issue
was already present before that commit as a possible use-after-free
of isec.

Shivnandan Kumar reported the list corruption and proposed
a patch to split the list and rcu elements out of the union
as separate fields of the inode_security_struct so that setting
the rcu element would not affect the list element.  However,
this would merely hide the issue and not truly fix the code.

This patch instead moves up the deletion of the list entry
prior to dropping the sbsec->isec_lock initially.  Then,
if the inode is dropped subsequently, there will be no further
references to the isec.

Reported-by: Shivnandan Kumar <shivnandan.k@samsung.com>
Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
Cc: stable@vger.kernel.org
Signed-off-by: Paul Moore <pmoore@redhat.com>
selinux: whitelist f2fs,sdcardfs,sdcardfskk,sdcardfsjb(psndna88)  [arter97]

selinux: whitelist f2fs
Most AOSP has already taken care of the new file-system, f2fs,
but TouchWiz still lacks support for f2fs.
Hardcode f2fs to SELinux's whitelist allows us to fully use f2fs with seclabel
without any sepolicy editing.

selinux: whitelist sdcardfs
To extend full, proper sdcardfs support to AOSP,
we need to add sdcardfs to selinux's whitelist
f2fs: update f2fs to dev branch with 3.0.y compatibility [arter97]
add v5.4 configs