linux-kernel - [PATCH 0/3] iio: adc: twl4030: Fix some error handling issues in 'twl4030_madc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 23 Sep 2017 08:03:34 +0200
From:   Christophe JAILLET <christophe.jaillet@...adoo.fr>
To:     jic23@...nel.org, knaack.h@....de, lars@...afoo.de,
        pmeerw@...erw.net, sre@...nel.org, wsa@...-dreams.de, kishon@...com
Cc:     linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
        kernel-janitors@...r.kernel.org,
        Christophe JAILLET <christophe.jaillet@...adoo.fr>
Subject: [PATCH 0/3] iio: adc: twl4030: Fix some  error handling issues in 'twl4030_madc_probe()'

These 3 patches are all related to error hangling in 'twl4030_madc_probe()'.
They are also all related to commit 7cc97d77ee8a
("iio: adc: twl4030: Fix ADC[3:6] readings")

The semantic of the patches behing slighly different:
   - direct return instead of going through the error handling path
   - missing function in the error handling path
   - spurious pattern (IMO) if unable to enable a regulator
I have splitted them in 3 parts.

Christophe JAILLET (3):
  iio: adc: twl4030: Fix an error handling path in
    'twl4030_madc_probe()'
  iio: adc: twl4030: Disable the vusb3v1 rugulator in the error handling
    path of 'twl4030_madc_probe()'
  iio: adc: twl4030: Return an error if we can not enable the vusb3v1
    regulator in 'twl4030_madc_probe()'

 drivers/iio/adc/twl4030-madc.c | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

-- 
2.11.0