linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	linux-iio@vger.kernel.org, jic23@kernel.org
Subject: Re: [PATCH 0/2] fixes for adt7410
Date: Mon, 16 Jul 2012 10:34:28 +0200	[thread overview]
Message-ID: <20120716083428.GD30009@pengutronix.de> (raw)
In-Reply-To: <50033218.7030602@metafoo.de>

On Sun, Jul 15, 2012 at 11:11:52PM +0200, Lars-Peter Clausen wrote:
> On 07/15/2012 10:40 PM, Hartmut Knaack wrote:
> > This patchset makes the ADT7410 usable. Main reason was the following error when trying to register one of these devices:
> > [  180.945561] BUG: unable to handle kernel NULL pointer dereference at   (null)
> > [  180.945592] IP: [<f84b1e80>] iio_device_register_eventset+0x380/0x3a0 [industrialio]
> > This happens, since in industrialio-events.c __iio_add_event_config_attrs (which does a INIT_LIST_HEAD) is not called, if the channels attribute of the device is not set. As a result, list_for_each_entry causes those NULL pointer dereference problems. So, before trying to access those list elements, we check for their existence (also in unregister functions).
> > Now the adt7410.c ended in some complex changes - my apologies for this:
> > 
> >   * check for exact values provided through sysfs, otherwise output a verbose error/usage message for: sample mode, resolution, event mode
> >   * adt7410_show_id: I don't see a point in masking out some LSBs, if they get shifted to oblivion, anyway -> no more need for ADT7410_MANUFACTORY_ID_MASK
> >   * adt7410_convert_temperature: in 13 bit mode, the driver assumed the data to be stored in bits 0-12, but according to the data sheet, it is stored in bits 3-15. Temperature readings were always around 200(°C), while real temperature was something around 20(°C). Simple fix: mask out bits 0-2 in 13 bit mode and use the 16 bit routines from that point on.
> >   * adt7410_set_t_bound: handle float values provided through sysfs properly. Also, simplify treatment of 13 bit values by masking out bits 0-2.
> >   * adt7410_probe, adt7410_remove: fix another possible NULL pointer dereference issue, in case no platform data is provided. Sync chip->config with the config register
> 
> Hi,
> 
> Sascha Hauer posted a couple of patches a while ago which seem to fix a
> similar set of issues.
> 
> See: http://www.spinics.net/lists/linux-iio/msg05947.html and
> http://www.spinics.net/lists/linux-iio/msg05955.html

Indeed, most if not all of the mentioned issues should be fixed already
with these patches.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2012-07-16  8:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15 20:40 [PATCH 0/2] fixes for adt7410 Hartmut Knaack
2012-07-15 21:11 ` Lars-Peter Clausen
2012-07-16  8:34   ` Sascha Hauer [this message]
2012-07-16  8:42     ` Jonathan Cameron
2012-07-16 19:37       ` Hartmut Knaack
2012-12-11 19:57       ` Hartmut Knaack
2012-12-11 20:10         ` Lars-Peter Clausen
2012-12-12  8:59           ` Jonathan Cameron
2012-12-12 10:08             ` Lars-Peter Clausen
2012-12-12 14:47               ` Guenter Roeck
2012-12-12 15:15                 ` Lars-Peter Clausen
2012-12-12 16:51                   ` Guenter Roeck
2012-12-12 17:09                     ` Lars-Peter Clausen
2012-12-12 19:10                 ` Hartmut Knaack

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=20120716083428.GD30009@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --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;
as well as URLs for NNTP newsgroup(s).