David S. Miller wrote:
From: Dave Jiang <djiang@xxxxxxxxxx>
Date: Wed, 17 Aug 2005 10:19:20 -0700
Should the kernel intercept the flags field at the point where it knows
whether it's invoking a 32bit call or 64bit and strip the flag if it
shouldn't be there to prevent something like this?
The flags field should be checked for invalid bits at
the socket call level before any of the MSG_CMSG_COMPAT
stuff runs.
I don't believe there are any code checking for invalid flag fields
currently. For example, sys_sendmsg() the first thing it does is check
MSG_CMSG_COMPAT flag and call get_compat_msghdr()..... should we be
putting in checking codes for flags?
Anyways, just wanted to run it by people that knows what's going on and
make sure it's not a serious problem.
--
Dave
------------------------------------------------------
Dave Jiang
Software Engineer Phone: (480) 517-0372
MontaVista Software, Inc. Fax: (480) 517-0262
2141 E Broadway Rd, St 108 Web: www.mvista.com
Tempe, AZ 85282 mailto:djiang@xxxxxxxxxx
------------------------------------------------------
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
