From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-irda@pasta.cs.uit.no
Subject: IrDA patches on the way...
Date: Wed, 7 Nov 2001 19:11:58 -0800 [thread overview]
Message-ID: <20011107191158.A23773@bougret.hpl.hp.com> (raw)
Hi,
After an important user reported a crash of the IrDA stack, I
did an audit of the disconnect/close code for race conditions. I also
kept in mine to looks for potential skb leaks. Well, that was some
work, but my quest was quite successfull ;-)
I also fixed a connection setup deadlock that was an old
friend eluding me. And I've been sent an endianess patch that is
necessary for operation on PPC.
Patches have been on the IrDA mailing list for one week and
have suffered my torture test since, so they are ready to go ;-)
Regards,
Jean
[FEATURE] : Add a new feature to the IrDA stack
[CORRECT] : Fix to have the correct/expected behaviour
[CRITICA] : Fix potential kernel crash
ir243_endian_fix.diff :
---------------------
<Patch from Michel Denzer and Benjamin Herrenschmidt>
o [CORRECT] Fix endianess in IrDA parameters management
Without this, the IrDA stack doesn't work on PPC :-(
ir243_usb_descr.diff :
--------------------
<First part is from Martin Diehl>
o [CORRECT] Use specific get class descriptor and not the standard one
o [FEATURE] Reduce verbosity of the driver
ir243_lap_lmp_races-2.diff :
--------------------------
o [CRITICA] Avoid race condition in LSAP closure
o [CORRECT] Remove potential skb leaks
o [CORRECT] Add MEDIA_BUSY_TIMER_EXPIRED event to avoid stack deadlock
o [CORRECT] Do a proper disconnect on RECV_RD_RSP
o [FEATURE] Cleanup handling of pending LAP connect & Ultra Tx
o [FEATURE] Add small busy delay after discovery indication
o [FEATURE] Remove discovery event postponing kludge
o [FEATURE] cleanups, comments
o [FEATURE] Reduce verbosity of the stack
ir243_ttp_sock_races-2.diff :
---------------------------
o [CRITICA] Avoid race condition in TSAP closure
o [CRITICA] Avoid race condition in socket closure
o [CRITICA] Avoid various race conditions in IrNET
o [CORRECT] Remove potential skb leaks
o [CORRECT] Remove IrNET discovery log leak
o [CORRECT] Don't export inline function (irda_lock)
o [FEATURE] Use skb_orphan() instead of skb_clone() + kfree_skb()
o [FEATURE] cleanups, comments
o [FEATURE] Reduce verbosity of the stack
ir245_help_obex.diff :
--------------------
o [FEATURE] Looks like somebody got confused about what IrOBEX is ;-)
next reply other threads:[~2001-11-08 3:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 3:11 Jean Tourrilhes [this message]
2001-11-30 20:54 Jean Tourrilhes
2002-01-09 20:00 Jean Tourrilhes
2002-03-05 22:32 Jean Tourrilhes
2002-04-03 2:17 Jean Tourrilhes
2002-04-19 2:27 Jean Tourrilhes
2002-05-10 22:40 Jean Tourrilhes
2002-06-11 0:51 Jean Tourrilhes
2002-07-16 20:53 Jean Tourrilhes
2002-08-06 20:48 Jean Tourrilhes
2002-12-02 23:36 Jean Tourrilhes
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=20011107191158.A23773@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jt@hpl.hp.com \
--cc=linux-irda@pasta.cs.uit.no \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®