From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: Bernard Pidoux <bernard.pidoux@upmc.fr>
Cc: linux-hams <linux-hams@vger.kernel.org>,
Ray Wells <vk2tv@exemail.com.au>,
Charlie k4gbb <k4gbb1@earthlink.net>,
Jerry DeLong <KD4YAL@tampabay.rr.com>, F1TE <f1te@f1te.org>,
f8arr <f8arr@f8arr.org>
Subject: Re: BUGs into libax25
Date: Mon, 2 Jun 2008 09:49:38 +0100 [thread overview]
Message-ID: <20080602084938.GB997@linux-mips.org> (raw)
In-Reply-To: <4843220B.20703@upmc.fr>
On Mon, Jun 02, 2008 at 12:26:19AM +0200, Bernard Pidoux wrote:
> I found a number of BUGs into libax25 that may affect nearly ALL AX25
> applications for it is in ax25_aton_entry() function that is used to
> translate a callsign into AX25 format.
> Programs like kissattach, listen, ax25ipd, FPAC, xfbbd are concerned.
>
> The code would return an error with 6 letters callsigns.
>
>
> The second set of errors is in /proc/ax25/ timers format description.
> since timers are now in millisec, they require a larger storage size.
> This results in using unsigned long integers rather than unsigned short
> integers.
>
> Ax25-tools and ax25-apps must be recompiled after recompilation and
> installation of this new libax25 version.
> FPAC and LinuxFBB also.
I guess that means we need to introduce symbol versions like glibc and a
few others. Oh pleassure, oh fun.
Ralf
next prev parent reply other threads:[~2008-06-02 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 22:26 BUGs into libax25 Bernard Pidoux
2008-06-02 2:14 ` Mike McCarthy, W1NR
2008-06-02 6:49 ` Robin Gilks
2008-06-02 9:16 ` Ralf Baechle DL5RB
2008-06-02 17:16 ` Dave Platt
2008-06-02 8:49 ` Ralf Baechle DL5RB [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-02 9:36 DL5DI
2008-06-02 10:41 ` Matti Aarnio
2008-06-02 16:28 ` Bernard Pidoux
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=20080602084938.GB997@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=KD4YAL@tampabay.rr.com \
--cc=bernard.pidoux@upmc.fr \
--cc=f1te@f1te.org \
--cc=f8arr@f8arr.org \
--cc=k4gbb1@earthlink.net \
--cc=linux-hams@vger.kernel.org \
--cc=vk2tv@exemail.com.au \
/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.