* double-check me?
@ 2003-08-17 17:45 Jeff Garzik
2003-08-17 20:58 ` Krzysztof Halasa
2003-08-17 21:34 ` Jason Lunz
0 siblings, 2 replies; 6+ messages in thread
From: Jeff Garzik @ 2003-08-17 17:45 UTC (permalink / raw)
To: Maillist netdev; +Cc: David S. Miller
Maybe you guys can spot something I'm missing here. alloc_netdev is
supposed to guarantee that dev->priv is aligned by 32 bytes:
struct net_device *alloc_netdev(int sizeof_priv, const char *mask,
void (*setup)(struct net_device *))
{
struct net_device *dev;
int alloc_size;
/* ensure 32-byte alignment of the private area */
alloc_size = sizeof (*dev) + sizeof_priv + 31;
dev = (struct net_device *) kmalloc (alloc_size, GFP_KERNEL);
if (dev == NULL)
{
printk(KERN_ERR "alloc_dev: Unable to allocate device
memory.\n"
);
return NULL;
}
memset(dev, 0, alloc_size);
if (sizeof_priv)
dev->priv = (void *) (((long)(dev + 1) + 31) & ~31);
Now... shouldn't that last line of code be "dev + 1 + sizeof(*dev)" ?
It seems to work 2.[456] for a long time, so I am doubting myself...
surely it would have caused memory corruption or something by now if I
have really found a bug.
Jeff
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: double-check me?
2003-08-17 17:45 double-check me? Jeff Garzik
@ 2003-08-17 20:58 ` Krzysztof Halasa
2003-08-17 22:31 ` Jeff Garzik
2003-08-17 21:34 ` Jason Lunz
1 sibling, 1 reply; 6+ messages in thread
From: Krzysztof Halasa @ 2003-08-17 20:58 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Maillist netdev, David S. Miller
Jeff Garzik <jgarzik@pobox.com> writes:
> Maybe you guys can spot something I'm missing here. alloc_netdev is
> supposed to guarantee that dev->priv is aligned by 32 bytes:
>
> struct net_device *dev;
>
> if (sizeof_priv)
> dev->priv = (void *) (((long)(dev + 1) + 31) & ~31);
>
>
> Now... shouldn't that last line of code be "dev + 1 + sizeof(*dev)" ?
>
> It seems to work 2.[456] for a long time, so I am doubting
> myself... surely it would have caused memory corruption or something
> by now if I have really found a bug.
Looks ok... not very readable, though.
dev + 1 = ((u8*)dev) + sizeof(dev) = pointer to end of net_device struct.
(X + 31) & ~31 makes sure X is 32-bytes aligned (0-31 bytes are added).
Hope the alloc_size has enough space for this.
31 should be better 0x1F I think.
I also like sizeof(struct net_device) more than sizeof(*dev).
Why do you want "+ 1" if you add sizeof(*dev)?
--
Krzysztof Halasa
Network Administrator
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: double-check me?
2003-08-17 17:45 double-check me? Jeff Garzik
2003-08-17 20:58 ` Krzysztof Halasa
@ 2003-08-17 21:34 ` Jason Lunz
1 sibling, 0 replies; 6+ messages in thread
From: Jason Lunz @ 2003-08-17 21:34 UTC (permalink / raw)
To: netdev
jgarzik@pobox.com said:
> if (sizeof_priv)
> dev->priv = (void *) (((long)(dev + 1) + 31) & ~31);
>
>
> Now... shouldn't that last line of code be "dev + 1 + sizeof(*dev)" ?
are you missing that the "dev + 1" pointer arithmetic is already adding
sizeof(*dev) to dev, rather than just 1 byte? "(dev + 1)" is a pointer
to the private area after the actual struct net_device, and
"((long)(dev + 1) + 31)" adds 31 bytes of padding. The final "& ~31"
chops off any excess padding from the 31 that was added and actually
aligns the pointer.
Seems right to me, but I'm not used to playing alignment tricks.
Jason
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: double-check me?
2003-08-17 20:58 ` Krzysztof Halasa
@ 2003-08-17 22:31 ` Jeff Garzik
2003-08-18 14:38 ` Jason Lunz
0 siblings, 1 reply; 6+ messages in thread
From: Jeff Garzik @ 2003-08-17 22:31 UTC (permalink / raw)
To: Krzysztof Halasa; +Cc: Maillist netdev, David S. Miller
Krzysztof Halasa wrote:
> Jeff Garzik <jgarzik@pobox.com> writes:
>
>
>>Maybe you guys can spot something I'm missing here. alloc_netdev is
>>supposed to guarantee that dev->priv is aligned by 32 bytes:
>>
>> struct net_device *dev;
>>
>> if (sizeof_priv)
>> dev->priv = (void *) (((long)(dev + 1) + 31) & ~31);
>>
>>
>>Now... shouldn't that last line of code be "dev + 1 + sizeof(*dev)" ?
>>
>>It seems to work 2.[456] for a long time, so I am doubting
>>myself... surely it would have caused memory corruption or something
>>by now if I have really found a bug.
>
>
> Looks ok... not very readable, though.
>
> dev + 1 = ((u8*)dev) + sizeof(dev) = pointer to end of net_device struct.
C pointer arithmatic. Ok, duh, thanks :)
Jeff, too used to void pointer arith
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: double-check me?
2003-08-17 22:31 ` Jeff Garzik
@ 2003-08-18 14:38 ` Jason Lunz
2003-08-18 14:41 ` Jeff Garzik
0 siblings, 1 reply; 6+ messages in thread
From: Jason Lunz @ 2003-08-18 14:38 UTC (permalink / raw)
To: netdev
jgarzik@pobox.com said:
> C pointer arithmatic. Ok, duh, thanks :)
> Jeff, too used to void pointer arith
Don't get _too_ used to it. arithmetic on (void *) is a gcc extension.
it's undefined in ansi C.
Jason
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: double-check me?
2003-08-18 14:38 ` Jason Lunz
@ 2003-08-18 14:41 ` Jeff Garzik
0 siblings, 0 replies; 6+ messages in thread
From: Jeff Garzik @ 2003-08-18 14:41 UTC (permalink / raw)
To: Jason Lunz; +Cc: netdev
On Mon, Aug 18, 2003 at 02:38:50PM +0000, Jason Lunz wrote:
> jgarzik@pobox.com said:
> > C pointer arithmatic. Ok, duh, thanks :)
> > Jeff, too used to void pointer arith
>
> Don't get _too_ used to it. arithmetic on (void *) is a gcc extension.
> it's undefined in ansi C.
Yes, I know.
It's used extensively in the kernel, however.
Jeff
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-08-18 14:41 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-08-17 17:45 double-check me? Jeff Garzik
2003-08-17 20:58 ` Krzysztof Halasa
2003-08-17 22:31 ` Jeff Garzik
2003-08-18 14:38 ` Jason Lunz
2003-08-18 14:41 ` Jeff Garzik
2003-08-17 21:34 ` Jason Lunz
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).