From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: samuel-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
irda-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC PATCH 0/9] IrDA 2.6.28 bug fix
Date: Sun, 14 Dec 2008 23:08:37 -0800 (PST) [thread overview]
Message-ID: <20081214.230837.169487041.davem@davemloft.net> (raw)
In-Reply-To: <20081215015729.587697008-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
From: Samuel Ortiz <samuel-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
Date: Mon, 15 Dec 2008 02:57:29 +0100
> This is a 9 patches series for IrDA, against your net-2.6 tree.
> This is an attempt to fix kernel.bugzilla.org bug #11795, where we noticed
> skb->cb could be altered once submitted to dev_queue_xmit. Since IrDA is using
> this callback to pass per-skb information, we are now stuffing it in front of
> skb->data, after allocating the right headroom.
>
> Another solution would be to play with the IrDA physical header and skb_pull
> our skbs whenever we are physically transmitting the data.
Hi Sam.
I appreciate you working on this.
But I there are two issues here:
1) There is no way I can put a series of 9 invasive patches like these
so late into 2.6.28
If we need to fix it in 2.6.28 it'd need to be a 5 to 10 line
change at most, even if hackish, before I could seriously consider
it.
2) Just like you can't claim ownership to skb->cb after dev_queue_xmit(),
you just as equally can't claim ownership to areas in front of
skb->data either.
I'm pretty sure we discussed how #2 wouldn't work for this problem.
I understand you need a way to pass information, but you're trying to
do it using things the IRDA (nor any other) stack does not own across
a dev_queue_xmit() invocation.
Furthermore, device layer schemes that try to use some shared
part of the skb for their communication is frail, and a good
way to see how frail it is is to consider how encapsulation of
such device types within themselves might be made to work.
You can't do it with skb->cb[] private storage, and you doubly can't
do it by sneaking things in front of skb->data because that's where
the encapsulated protocol headers would go.
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
next prev parent reply other threads:[~2008-12-15 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 1:57 [RFC PATCH 0/9] IrDA 2.6.28 bug fix Samuel Ortiz
2008-12-15 1:57 ` [RFC PATCH 1/9] irda: Introduce irda_alloc_skb Samuel Ortiz
2008-12-15 1:57 ` [RFC PATCH 2/9] irda: stack should call irda_get_skb_cb() Samuel Ortiz
2008-12-15 1:57 ` [RFC PATCH 3/9] irda: IrDA drivers " Samuel Ortiz
2008-12-15 1:57 ` [RFC PATCH 4/9] irda: reserve irda_skb on sock_alloc_send_skb() skbs Samuel Ortiz
2008-12-15 1:57 ` [RFC PATCH 5/9] irda: Introduce irda_dev_alloc_skb Samuel Ortiz
2008-12-15 1:57 ` [RFC PATCH 6/9] irda: Drivers should use irda_dev_alloc_skb() on the RX path Samuel Ortiz
2008-12-15 1:57 ` [RFC PATCH 7/9] irda: Stack RX path callers should use irda_dev_alloc_skb Samuel Ortiz
2008-12-15 1:57 ` [RFC PATCH 8/9] irda: Add a WARN_ON when our head room is too small Samuel Ortiz
2008-12-15 1:57 ` [RFC PATCH 9/9] irda: Fix irda_skb_cb size Samuel Ortiz
[not found] ` <20081215015729.587697008-jcdQHdrhKHMdnm+yROfE0A@public.gmane.org>
2008-12-15 7:08 ` David Miller [this message]
2008-12-15 12:31 ` [irda-users] [RFC PATCH 0/9] IrDA 2.6.28 bug fix Samuel Ortiz
2008-12-17 7:59 ` 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=20081214.230837.169487041.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=irda-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=samuel-jcdQHdrhKHMdnm+yROfE0A@public.gmane.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 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).