From: Bernard Pidoux <bpidoux@free.fr>
To: David Miller <davem@davemloft.net>
Cc: ralf@linux-mips.org, linux-hams@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] ax25.h unsigned long type for ax25 timers
Date: Thu, 19 Jun 2008 18:28:46 +0200 [thread overview]
Message-ID: <485A893E.4080405@free.fr> (raw)
In-Reply-To: <20080617.223050.266166325.davem@davemloft.net>
David,
Unfortunately I don't quite understand exactly why a structure in user
space cannot be changed.
But this means that I have to make some effort to learn a bit more about
the kernel structure and userspace.
However, thank you for your explanation about how to fix the discrepancy
between both timer structures.
I will try to dig out more information on this subject.
Bernard Pidoux, f6bvp
David Miller a écrit :
> From: Bernard Pidoux <bpidoux@free.fr>
> Date: Tue, 17 Jun 2008 15:04:38 +0200
>
>
>> In linux/include/linux/ax25.h
>> ax25_info_struct timers types remain unsigned
>>
>> struct ax25_info_struct {
>> unsigned int n2, n2count;
>> unsigned int t1, t1timer;
>> unsigned int t2, t2timer;
>> unsigned int t3, t3timer;
>> unsigned int idle, idletimer;
>> .....
>> };
>>
>> while in linux/include/net/ax25.h timers are unsigned long according
>> to kernel 2.6 timers.
>>
>> typedef struct ax25_cb {
>> .....
>> struct timer_list t1timer, t2timer, t3timer, idletimer;
>> unsigned long t1, t2, t3, idle, rtt;
>> ....
>>
>> Although ax25_info_struct is not much used it is refered at least
>> into libax25 and xfbb BBS application program.
>>
>> It seems thus reasonable to make the change.
>>
>> Signed-off-by: Bernard Pidoux <f6bvp@amsat.org>
>>
>
> Unfortunately this datastructure is exported to userspace,
> and therefore we cannot change the structure layout without
> breaking userspace.
>
> We cannot, as a result, make this change.
>
> The only way to fix this is to make a new fixed structure, and add new
> ax25 calls that accept this new structure.
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-19 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 13:04 [PATCH] ax25.h unsigned long type for ax25 timers Bernard Pidoux
2008-06-18 5:30 ` David Miller
2008-06-19 16:28 ` Bernard Pidoux [this message]
2008-06-19 21:46 ` David Miller
2008-06-19 22:38 ` Bernard Pidoux
2008-06-20 13:17 ` Bernard Pidoux F6BVP
2008-06-28 2:33 ` David Miller
2008-06-19 19:38 ` Al
2008-06-19 20:35 ` Al
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=485A893E.4080405@free.fr \
--to=bpidoux@free.fr \
--cc=davem@davemloft.net \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
/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.