[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <53A04FDA.6070101@oracle.com>
Date: Tue, 17 Jun 2014 22:25:30 +0800
From: Jeff Liu <jeff.liu@...cle.com>
To: gregkh@...uxfoundation.org
CC: Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...two.org>,
Pekka Enberg <penberg@...nel.org>,
Matt Mackall <mpm@...enic.com>, benh@...nel.crashing.org,
paulus@...ba.org, schwidefsky@...ibm.com,
heiko.carstens@...ibm.com, herbert@...dor.apana.org.au,
davem@...emloft.net, stefanr@...6.in-berlin.de, joro@...tes.org,
jejb@...isc-linux.org, deller@....de, bhelgaas@...gle.com,
clm@...com, Josef Bacik <jbacik@...com>, swhiteho@...hat.com,
bharrosh@...asas.com, bhalevy@...marydata.com, ccaulfie@...hat.com,
teigland@...hat.com, "Theodore Ts'o" <tytso@....edu>,
adilger.kernel@...ger.ca, jaegeuk@...nel.org,
cm224.lee@...sung.com, Mark Fasheh <mfasheh@...e.com>,
Joel Becker <jlbec@...lplan.org>, casey@...aufler-ca.com,
LKML <linux-kernel@...r.kernel.org>
Subject: [patch 00/24] lib/kobject: kset_create_and_add return error clean
up
Hello,
Currently, to verify if kset_create_and_add() is succeed or not, almost
all subsystems with sysfs support are check up the return value against
NULL, then return -ENOMEM on failure, since kset_create_and_add() always
return NULL in case of anything wrong. However, kset_register() can fail
due to other reasons, hence it's better to return the actual error on
kset_create_and_add(), this patch series is just did that and this is
inspired by Christoph in another thread:
http://www.spinics.net/lists/linux-mm/msg74729.html
Jeff Liu (24)
kobject: return actual error on kset_create_and_add
sample/kobject: update kset-example code
slub: return actual error on sysfs_slab_add
powerpc: check/return acutal error on sysfs init
s390: check/return actual error on sysfs init
crypt: return actual error code on pcrypt_init
kernel: return actual error on param_sysfs_init
drivers/firmware: return actual error on sysfs init
drivers/iommu: check actual error on iommu_init
drivers/base: return actual error on sysfs init
drviers/scsi: check sysfs init return value via IS_ERR at iscsi_boot_create_kset
drivers/parisc: return actual error on pdc_stable_init
drivers/pci: return actual error on pci_slot_init
drivers/s390: return actual error on sysfs init functions
drivers/of: return actual error on of_init
btrfs: return actual error on btrfs_init_sysfs
gfs2: return actual error on gfs2_sys_init
exofs: return actual error on exofs_sysfs_odev_add
fs/dlm: return actual error on dlm_lockspace_init
ext4: return actual error on ext4_init_fs
f2fs: return actual error on init_f2fs_fs
ocfs2: return actual error on sysfs init
net: return actual error on register_queue_kobjects
security/smack: return acutal error on smk_init_sysfs
Cheers,
-Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists