linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Bill Fink <billfink@mindspring.com>
To: mlan@cpu.lu
Cc: bcollins@debian.org, linux1394-devel@lists.sourceforge.net,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Firewire Disk Broken in 2.4.19-pre8-ben0 kernel (was working fine with 2.4.18-ben0)
Date: Tue, 14 May 2002 22:49:27 -0400	[thread overview]
Message-ID: <20020514224927.0078b3b5.billfink@mindspring.com> (raw)
In-Reply-To: <E177VJp-00007m-00@piglet.grunz.lu>


Hi Michel,

Nice shot!  It works again with the ieee1394-473 tarball (or the distributed
2.4.19-pre8 ieee1394 code) and the change you suggested.  Thanks a ton!!!

						-Bill



On Tue, 14 May 2002, Michel Lanners wrote:

> Shot in the dark....
>
> On  14 May, this message from Bill Fink echoed through cyberspace:
> > diff -u ieee1394-022602/hosts.c ieee1394-022702/hosts.c
> > --- ieee1394-022602/hosts.c	Sat Feb  9 00:41:40 2002
> > +++ ieee1394-022702/hosts.c	Tue Feb 26 15:06:39 2002
> > @@ -78,26 +97,39 @@
> >          spin_unlock_irqrestore(&hosts_lock, flags);
> >  }
> >
> > +/**
> > + * hpsb_alloc_host - allocate a new host controller.
> > + * @drv: the driver that will manage the host controller
> > + * @extra: number of extra bytes to allocate for the driver
> > + *
> > + * Allocate a &hpsb_host and initialize the general subsystem specific
> > + * fields.  If the driver needs to store per host data, as drivers
> > + * usually do, the amount of memory required can be specified by the
> > + * @extra parameter.  Once allocated, the driver should initialize the
> > + * driver specific parts, enable the controller and make it available
> > + * to the general subsystem using hpsb_add_host().
> > + *
> > + * The &hpsb_host is allocated with an single initial reference
> > + * belonging to the driver.  Once the driver is done with the struct,
> > + * for example, when the driver is unloaded, it should release this
> > + * reference using hpsb_unref_host().
> > + *
> > + * Return Value: a pointer to the &hpsb_host if succesful, %NULL if
> > + * no memory was available.
> > + */
> > +
> >  struct hpsb_host *hpsb_alloc_host(struct hpsb_host_driver *drv, size_t extra)
> >  {
> >          struct hpsb_host *h;
> >
> > -        h = kmalloc(sizeof(struct hpsb_host), SLAB_KERNEL);
> > +        h = kmalloc(sizeof(struct hpsb_host) + extra, SLAB_KERNEL);
> >          if (!h) return NULL;
> >          memset(h, 0, sizeof(struct hpsb_host));
>                         ^^^^^^^^^^^^^^^^^^^^^^^^
> This should probably be sizeof(struct hpsb_host) + extra.
>
> >
> > -	/* Drivers usually use this to allocate their private data */
> > -	if (extra) {
> > -		h->hostdata = kmalloc(extra, SLAB_KERNEL);
> > -		if (!h->hostdata) {
> > -			kfree(h);
> > -			return NULL;
> > -		}
> > -		memset(h->hostdata, 0, extra);
> > -	}
> > -
> > +	h->hostdata = h + 1;
> >          h->driver = drv;
> >          h->ops = drv->ops;
> > +	h->refcount = 1;
> >
> >          INIT_LIST_HEAD(&h->pending_packets);
> >          spin_lock_init(&h->pending_pkt_lock);

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2002-05-15  2:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13 14:55 Firewire Disk Broken in 2.4.19-pre8-ben0 kernel (was working fine with 2.4.18-ben0) Bill Fink
2002-05-13 15:13 ` Ben Collins
2002-05-13 16:07   ` Bill Fink
2002-05-13 16:09     ` Ben Collins
2002-05-13 17:29       ` benh
2002-05-14  4:40       ` Bill Fink
2002-05-14  5:57         ` Michel Lanners
2002-05-14 13:09           ` Ben Collins
2002-05-15  2:49           ` Bill Fink [this message]

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=20020514224927.0078b3b5.billfink@mindspring.com \
    --to=billfink@mindspring.com \
    --cc=bcollins@debian.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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).