public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Forest Bond <forest@alittletooquiet.net>
Cc: Greg KH <gregkh@suse.de>,
	Alexander Beregalov <a.beregalov@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Staging: vt6656 ?
Date: Mon, 6 Jul 2009 17:33:00 +0200	[thread overview]
Message-ID: <200907061733.01136.bzolnier@gmail.com> (raw)
In-Reply-To: <20090702182208.GD9422@alittletooquiet.net>

On Thursday 02 July 2009 20:22:08 Forest Bond wrote:
> Hi,
> 
> On Thu, Jul 02, 2009 at 07:45:49PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Sunday 28 June 2009 18:47:16 Forest Bond wrote:
> > > On Sun, Jun 28, 2009 at 05:59:45PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > > > [ I'll later setup vt665x branch of my misc.git tree, merge your patches,
> > > >   merge all outstanding vt6655 patches from Alexander and investigate a bit
> > > >   more whether merge of vt665x drivers is feasible and what needs to be
> > > >   done if so.. ]
> > > 
> > > Good.
> > 
> > The temporary tree is here:
> > 
> > git://git.kernel.org:/pub/scm/linux/kernel/git/bart/misc.git vt665x
> > 
> > and I'll happily apply patches to it till Greg digs out from under the
> > overdue patch queues.. :)
> 
> Thanks for doing this, Bartlomiej.
> 
> > > FYI, there is a known issue with the drivers as I've submitted them that causes
> > > lock-ups.  Please see the attached message for a suggested fix.
> > 
> > I think that all netdev_priv() changes should be reverted for now:
> 
> I'm happy to defer to you on this.  I don't really understand the code, to be
> frank.  However, if those changes are simply reverted, the driver will not
> compile.  I assume that you mean those areas should be removed?

Uh, you're right.. we need to use netdev_priv().

> > --- a/drivers/staging/vt6655/wpactl.c
> > +++ b/drivers/staging/vt6655/wpactl.c
> > @@ -112,14 +112,17 @@ static void wpadev_setup(struct net_device *dev)
> >  
> >  static int wpa_init_wpadev(PSDevice pDevice)
> >  {
> > +    PSDevice wpadev_priv;
> >  	struct net_device *dev = pDevice->dev;
> >           int ret=0;
> >  
> > -	pDevice->wpadev = alloc_netdev(0, "vntwpa", wpadev_setup);
> > +	pDevice->wpadev = alloc_netdev(sizeof(PSDevice), "vntwpa", wpadev_setup);
> >  	if (pDevice->wpadev == NULL)
> >  		return -ENOMEM;
> >  
> > -	pDevice->wpadev->priv = pDevice;
> > +    wpadev_priv = netdev_priv(pDevice->wpadev);
> > +    *wpadev_priv = *pDevice;
> > +
> >  	memcpy(pDevice->wpadev->dev_addr, dev->dev_addr, U_ETHER_ADDR_LEN);
> >           pDevice->wpadev->base_addr = dev->base_addr;
> >  	pDevice->wpadev->irq = dev->irq;
> > 
> > This will copy the current state of pDevice to newly allocated private part
> > of ->apdev but later modifications to the original pDevice won't be seen if
> > we access it through netdev_priv(pDevice->apdev) instead of apdev->priv.

[ it should be wpadev not apdev in the above description ]

> > [ I don't know whether this is a problem currently but it looks suspicious. ]
> 
> Agreed.  I gave this a best effort, but was not very confident about the result.

The code is puzzling (at best) -- I still don't know why do we need separate
netdev structure for hostap or wpactl functionality..

> Feel free to aggressively rework my changes if it seems appropriate.

I don't think there is a need for it and I would like to avoid that
since I'm also involved in other drivers/staging/ drivers (besides you
and Alexander are doing just fine :).

Seems like all we need to do to fix the problem is:

* fix code in hostap to also use alloc_netdev()

* bring back "manual" allocation of PSDevice structure
 
* use private netdev areas only to store the pointer to the single PSDevice
  structure that we allocate "manually" (requires converting all netdev_priv()
  instances to *netdev_priv() etc but the change should be straightforward).

  reply	other threads:[~2009-07-06 15:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 10:31 Staging: vt6656 ? Alexander Beregalov
2009-06-09 10:51 ` Greg KH
2009-06-09 11:33   ` Forest Bond
2009-06-28 13:43     ` Bartlomiej Zolnierkiewicz
2009-06-28 13:57       ` Forest Bond
2009-06-28 15:59         ` Bartlomiej Zolnierkiewicz
2009-06-28 16:47           ` Forest Bond
2009-07-02 17:45             ` Bartlomiej Zolnierkiewicz
2009-07-02 18:22               ` Forest Bond
2009-07-06 15:33                 ` Bartlomiej Zolnierkiewicz [this message]
2009-06-28 17:02           ` [PATCH 1/8] Add pristine upstream vt6656 driver sources to drivers/staging/vt6656 Forest Bond
2009-06-28 17:02           ` [PATCH 2/8] Add includes " Forest Bond
2009-06-28 17:03           ` [PATCH 3/8] Build vt6656.ko, not vntwusb.ko Forest Bond
2009-06-28 17:03           ` [PATCH 4/8] drivers/staging/vt6656/main_usb.c: Drop obsolete fsuid/fsgid accesses Forest Bond
2009-06-28 17:03           ` [PATCH 5/8] vt6656: Replace net_device->priv accesses with netdev_priv calls Forest Bond
2009-06-28 17:03           ` [PATCH 6/8] vt6656: use net_device_ops for management functions Forest Bond
2009-06-28 17:03           ` [PATCH 7/8] vt6656: replace call to info with printk call Forest Bond
2009-06-28 17:03           ` [PATCH 8/8] Integrate drivers/staging/vt6656 into build system Forest Bond
2009-06-28 16:29         ` Staging: vt6656 ? Greg KH
2009-06-28 16:40           ` Forest Bond

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=200907061733.01136.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=a.beregalov@gmail.com \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.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