From: Marcel Holtmann <marcel@holtmann.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/4] fix endianness bug in l2cap_sock_listen()
Date: Fri, 27 Jul 2007 16:41:18 +0200 [thread overview]
Message-ID: <1185547278.13228.15.camel@violet> (raw)
In-Reply-To: <E1IEPNS-0005RS-7o@ZenIV.linux.org.uk>
Hi Al,
> We loop through psm values, calling __l2cap_get_sock_by_addr(psm, ...)
> until we get NULL; then we set ->psm of our socket to htobs(psm).
> IOW, we find unused psm value and put it into our socket. So far, so
> good, but... __l2cap_get_sock_by_addr() compares its argument with
> ->psm of sockets. IOW, the entire thing works correctly only on
> little-endian. On big-endian we'll get "no socket with such psm"
> on the first iteration, since we won't find a socket with ->psm == 0x1001.
> We will happily conclude that 0x1001 is unused and slap htobs(0x1001)
> (i.e. 0x110) into ->psm of our socket. Of course, the next time around
> the same thing will repeat and we'll just get a fsckload of sockets
> with the same ->psm assigned.
>
> Fix: pass htobs(psm) to __l2cap_get_sock_by_addr() there. All other
> callers are already passing little-endian values and all places that
> store something in ->psm are storing little-endian.
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Dave, all four patches are good and should go in sooner than later. If
you want me to put them into my tree first, then I can do that or you
can apply them directly. You choice.
Regards
Marcel
next prev parent reply other threads:[~2007-07-27 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 12:57 [PATCH 1/4] fix endianness bug in l2cap_sock_listen() Al Viro
2007-07-27 14:41 ` Marcel Holtmann [this message]
2007-07-29 7:16 ` David Miller
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=1185547278.13228.15.camel@violet \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).