Linux IIO development
 help / color / mirror / Atom feed
From: Hartmut Knaack <knaack.h@gmx.de>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org, jic23@kernel.org
Subject: Re: [PATCH 1/2] fixes for adt7410
Date: Mon, 16 Jul 2012 21:26:42 +0200	[thread overview]
Message-ID: <50046AF2.8020907@gmx.de> (raw)
In-Reply-To: <5003E635.8080200@metafoo.de>

Lars-Peter Clausen schrieb:
> On 07/15/2012 11:50 PM, Hartmut Knaack wrote:
>> Lars-Peter Clausen schrieb:
>>> On 07/15/2012 10:40 PM, Hartmut Knaack wrote:
>>>> This patch adds some checks prior to accessing device attribute lists in industrialio-event.c.
>>>>
>>>> Signed-off-by: Harmut Knaack <knaack.h@gmx.de>
>>>> ---
>>>> diff --git a/drivers/iio/industrialio-event.c b/drivers/iio/industrialio-event.c
>>>> index b49059d..fe68e90 100644
>>>> --- a/drivers/iio/industrialio-event.c
>>>> +++ b/drivers/iio/industrialio-event.c
>>>> @@ -425,11 +425,13 @@ int iio_device_register_eventset(struct iio_dev *indio_dev)
>>>>                 *attrcount_orig);
>>>>      attrn = attrcount_orig;
>>>>      /* Add all elements from the list. */
>>>> -    list_for_each_entry(p,
>>>> -                &indio_dev->event_interface->dev_attr_list,
>>>> -                l)
>>>> -        indio_dev->event_interface->group.attrs[attrn++] =
>>>> -            &p->dev_attr.attr;
>>>> +    if (indio_dev->event_interface->dev_attr_list.next)
>>> next should never be NULL. If it is this means that INIT_LIST_HEAD has not
>>> been called on the list and the correct fix is to make sure that it is called.
>> Exactly. If the channels-attributes have not been set, INIT_LIST_HEAD (called through __iio_add_event_config_attrs) is not called. So, should we just stop instantiating the device if it does not have channel information?
> The correct fix is to call INIT_LIST_HEAD right after the struct which
> contains the list has been allocated. Sascha already sent a patch which does
> this as well. See: http://www.spinics.net/lists/linux-iio/msg05946.html
>
> - Lars
>
Alright, never mind then. I'm looking forward to see those changes in mainline kernel :-)

Hartmut

      reply	other threads:[~2012-07-16 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15 20:40 [PATCH 1/2] fixes for adt7410 Hartmut Knaack
2012-07-15 20:59 ` Lars-Peter Clausen
2012-07-15 21:50   ` Hartmut Knaack
2012-07-16 10:00     ` Lars-Peter Clausen
2012-07-16 19:26       ` Hartmut Knaack [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=50046AF2.8020907@gmx.de \
    --to=knaack.h@gmx.de \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@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