Revision 98bcd08b5bfe78c1c9bda5768aa081e0fe4fcc4f authored by Marcel Holtmann on 14 July 2006, 09:42:12 UTC, committed by David S. Miller on 24 July 2006, 19:44:25 UTC
Some Bluetooth RFCOMM implementations try to negotiate a bigger channel MTU than we can support for a particular session. The maximum MTU for a RFCOMM session is limited through the L2CAP layer. So if the other side proposes a channel MTU that is bigger than the underlying L2CAP MTU, we should reduce it to the L2CAP MTU of the session minus five bytes for the RFCOMM headers. Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
1 parent 2266d88
| File | Mode | Size |
|---|---|---|
| Kconfig | -rw-r--r-- | 10.5 KB |
| Makefile | -rw-r--r-- | 1.1 KB |
| aes.c | -rw-r--r-- | 11.6 KB |
| anubis.c | -rw-r--r-- | 27.8 KB |
| api.c | -rw-r--r-- | 6.4 KB |
| arc4.c | -rw-r--r-- | 2.1 KB |
| blowfish.c | -rw-r--r-- | 17.5 KB |
| cast5.c | -rw-r--r-- | 34.2 KB |
| cast6.c | -rw-r--r-- | 21.5 KB |
| cipher.c | -rw-r--r-- | 11.1 KB |
| compress.c | -rw-r--r-- | 1.5 KB |
| crc32c.c | -rw-r--r-- | 2.5 KB |
| crypto_null.c | -rw-r--r-- | 3.3 KB |
| deflate.c | -rw-r--r-- | 5.4 KB |
| des.c | -rw-r--r-- | 35.4 KB |
| digest.c | -rw-r--r-- | 2.8 KB |
| hmac.c | -rw-r--r-- | 3.1 KB |
| internal.h | -rw-r--r-- | 2.8 KB |
| khazad.c | -rw-r--r-- | 51.9 KB |
| md4.c | -rw-r--r-- | 6.2 KB |
| md5.c | -rw-r--r-- | 7.2 KB |
| michael_mic.c | -rw-r--r-- | 3.5 KB |
| proc.c | -rw-r--r-- | 2.8 KB |
| scatterwalk.c | -rw-r--r-- | 2.8 KB |
| scatterwalk.h | -rw-r--r-- | 2.0 KB |
| serpent.c | -rw-r--r-- | 20.0 KB |
| sha1.c | -rw-r--r-- | 3.1 KB |
| sha256.c | -rw-r--r-- | 11.0 KB |
| sha512.c | -rw-r--r-- | 10.3 KB |
| tcrypt.c | -rw-r--r-- | 34.3 KB |
| tcrypt.h | -rw-r--r-- | 103.9 KB |
| tea.c | -rw-r--r-- | 7.3 KB |
| tgr192.c | -rw-r--r-- | 31.1 KB |
| twofish.c | -rw-r--r-- | 45.0 KB |
| wp512.c | -rw-r--r-- | 60.3 KB |
Computing file changes ...
