public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Daniel Stekloff <dsteklof@us.ibm.com>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>
Subject: Re: scsi_id segfault with udev-009
Date: Wed, 17 Dec 2003 21:40:09 +0200	[thread overview]
Message-ID: <1071690009.11705.2.camel@nosferatu.lan> (raw)
In-Reply-To: <200312171017.28358.dsteklof@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]

On Wed, 2003-12-17 at 20:17, Daniel Stekloff wrote:
> On Wednesday 17 December 2003 09:29 am, Martin Schlemmer wrote:
> > Hi
> >
> > Getting this with scsi_id and udev-009:
> 
> 
> Hi,
> 
> Scsi_id hasn't been changed to use the latest libsysfs changes. The 
> "directory" in the sysfs_class_device is now considered "private" and only 
> should be accessed using functions. Treating the structures as handles lets 
> us only load information when it's needed, reducing caching or stale 
> information and also helping performance. 
> 
> Here's the problem.
> 
> static inline char *sysfs_get_attr(struct sysfs_class_device *dev,
>                                     const char *attr)
> {
>         return sysfs_get_value_from_attributes(dev->directory->attributes,
>                                                attr);
> }
> 
> Please try this quick fix:
> 

Yep, that fixes it, thanks.  Btw, any reason it wont actually display
anything ?


Thanks,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-12-17 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17 17:29 scsi_id segfault with udev-009 Martin Schlemmer
2003-12-17 18:07 ` Greg KH
2003-12-17 18:17 ` Daniel Stekloff
2003-12-17 19:40   ` Martin Schlemmer [this message]
2003-12-17 19:43     ` Daniel Stekloff
2003-12-17 21:09       ` Martin Schlemmer
2003-12-18  0:36   ` Greg KH

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=1071690009.11705.2.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=dsteklof@us.ibm.com \
    --cc=greg@kroah.com \
    --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