From: David Miller <davem@davemloft.net>
To: sjur.brandeland@stericsson.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/5] caif: Fixes freeze on Link layer removal.
Date: Sun, 22 May 2011 20:13:40 -0400 (EDT) [thread overview]
Message-ID: <20110522.201340.445758096505075998.davem@davemloft.net> (raw)
In-Reply-To: <1306099134-12989-2-git-send-email-sjur.brandeland@stericsson.com>
From: Sjur Brændeland <sjur.brandeland@stericsson.com>
Date: Sun, 22 May 2011 23:18:51 +0200
> CAIF Socket layer - caif_socket.c:
> - Plug mem-leak at reconnect.
> - Always call disconnect to cleanup CAIF stack.
> - Disconnect will always report success.
>
> CAIF configuration layer - cfcnfg.c
> - Disconnect must dismantle the caif stack correctly
> - Protect against faulty removals (check on id zero)
>
> CAIF mux layer - cfmuxl.c
> - When inserting new service layer in the MUX remove
> any old entries with the same ID.
> - When removing CAIF Link layer, remove the associated
> service layers before notifying service layers.
>
> Signed-off-by: Sjur Brændeland <sjur.brandeland@stericsson.com>
Applied.
next prev parent reply other threads:[~2011-05-23 0:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 21:18 [PATCH 1/5] caif: Bugfix add check NULL pointer before calling functions Sjur Brændeland
2011-05-22 21:18 ` [PATCH 2/5] caif: Fixes freeze on Link layer removal Sjur Brændeland
2011-05-23 0:13 ` David Miller [this message]
2011-05-22 21:18 ` [PATCH 3/5] caif: Fix freezes when running CAIF loopback device Sjur Brændeland
2011-05-23 0:13 ` David Miller
2011-05-22 21:18 ` [PATCH 4/5] caif: Update documentation of CAIF transmit and receive functions Sjur Brændeland
2011-05-23 0:13 ` David Miller
2011-05-22 21:18 ` [PATCH 5/5] caif: Plug memory leak for checksum error Sjur Brændeland
2011-05-23 0:14 ` David Miller
2011-05-23 0:13 ` [PATCH 1/5] caif: Bugfix add check NULL pointer before calling functions 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=20110522.201340.445758096505075998.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sjur.brandeland@stericsson.com \
/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).