From: Andreas Schwab <schwab@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: olh@suse.de, linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH] compat bug in sys_recvmsg, MSG_CMSG_COMPAT check missing
Date: Sun, 06 Jun 2004 00:05:58 +0200 [thread overview]
Message-ID: <jeise57j95.fsf@sykes.suse.de> (raw)
In-Reply-To: <20040605145333.11c80173.davem@redhat.com> (David S. Miller's message of "Sat, 5 Jun 2004 14:53:33 -0700")
"David S. Miller" <davem@redhat.com> writes:
> On Sat, 05 Jun 2004 23:47:22 +0200
> Andreas Schwab <schwab@suse.de> wrote:
>
>> > Olaf's patch, it said:
>> >
>> > - if (flags & ~(MSG_PEEK|MSG_DONTWAIT|MSG_TRUNC))
>> > + if (flags & ~(MSG_PEEK|MSG_DONTWAIT|MSG_TRUNC|MSG_CMSG_COMPAT))
>>
>> Yes, and where is the problem?
>
> If MSG_CMSG_COMPAT is "ZERO", which it will be if CONFIG_COMPAT is
> not set, then "~0" is all bits, therefore if any bit (even the ones
> we want to accept) is set we will return failure. The test ends
> up amounting to:
>
> if (flags & ~0)
>
> which is true if any bit is set, that's not what we want.
Can you say DeMorgan?
> diff -Nru a/include/linux/socket.h b/include/linux/socket.h
> --- a/include/linux/socket.h 2004-06-05 14:53:34 -07:00
> +++ b/include/linux/socket.h 2004-06-05 14:53:34 -07:00
> @@ -241,8 +241,10 @@
>
> #if defined(CONFIG_COMPAT)
> #define MSG_CMSG_COMPAT 0x80000000 /* This message needs 32 bit fixups */
> +#define MSG_FLAGS_USER(X) ((X) & ~MSG_CMSG_COMPAT)
> #else
> #define MSG_CMSG_COMPAT 0 /* We never have 32 bit fixups */
> +#define MSG_FLAGS_USER(X) (X)
> #endif
>
>
> diff -Nru a/net/appletalk/ddp.c b/net/appletalk/ddp.c
> --- a/net/appletalk/ddp.c 2004-06-05 14:53:35 -07:00
> +++ b/net/appletalk/ddp.c 2004-06-05 14:53:35 -07:00
> @@ -1567,7 +1567,7 @@
> struct atalk_route *rt;
> int err;
>
> - if (flags & ~MSG_DONTWAIT)
> + if (MSG_FLAGS_USER(flags) & ~MSG_DONTWAIT)
> return -EINVAL;
>
> if (len > DDP_MAXSZ)
This is exactly equivalent to Olaf's version.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-06-05 22:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 20:43 [PATCH] compat bug in sys_recvmsg, MSG_CMSG_COMPAT check missing Olaf Hering
2004-06-05 21:01 ` David S. Miller
2004-06-05 21:05 ` David S. Miller
2004-06-05 21:21 ` Andreas Schwab
2004-06-05 21:36 ` David S. Miller
2004-06-05 21:47 ` Andreas Schwab
2004-06-05 21:53 ` David S. Miller
2004-06-05 22:05 ` Andreas Schwab [this message]
2004-06-05 22:29 ` David S. Miller
2004-06-05 22:37 ` Olaf Hering
2004-06-05 22:55 ` David S. Miller
2004-06-05 21:17 ` Olaf Hering
2004-06-05 21:37 ` David S. Miller
2004-06-05 21:14 ` Olaf Hering
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=jeise57j95.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=olh@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.