diff options
author | Eric Paris <eparis@parisplace.org> | 2005-06-30 09:58:51 (GMT) |
---|---|---|
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-06-30 15:45:09 (GMT) |
commit | 6931dfc9f3f81d148b7ed0ab3fd796f8b986a995 (patch) | |
tree | 8c7251413b1243e29dc155fd9590931b423c5e31 /include/asm-m32r/byteorder.h | |
parent | 9a936eb928c1a253c2e5d66b947688bdc55094a6 (diff) | |
download | linux-fsl-qoriq-6931dfc9f3f81d148b7ed0ab3fd796f8b986a995.tar.xz |
[PATCH] selinux_sb_copy_data() should not require a whole page
Currently selinux_sb_copy_data requires an entire page be allocated to
*orig when the function is called. This "requirement" is based on the fact
that we call copy_page(in_save, nosec_save) and in_save = orig when the
data is not FS_BINARY_MOUNTDATA. This means that if a caller were to call
do_kern_mount with only about 10 bytes of options, they would get passed
here and then we would corrupt PAGE_SIZE - 10 bytes of memory (with all
zeros.)
Currently it appears all in kernel FS's use one page of data so this has
not been a problem. An out of kernel FS did just what is described above
and it would almost always panic shortly after they tried to mount. From
looking else where in the kernel it is obvious that this string of data
must always be null terminated. (See example in do_mount where it always
zeros the last byte.) Thus I suggest we use strcpy in place of copy_page.
In this way we make sure the amount we copy is always less than or equal to
the amount we received and since do_mount is zeroing the last byte this
should be safe for all.
Signed-off-by: Eric Paris <eparis@parisplace.org>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>
Acked-by: James Morris <jmorris@redhat.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'include/asm-m32r/byteorder.h')
0 files changed, 0 insertions, 0 deletions