summaryrefslogtreecommitdiff
path: root/tools/lib/traceevent/Build
blob: c681d0575d167cf746d8ca2a0ae2a17124068e67 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
libtraceevent-y += event-parse.o
libtraceevent-y += event-plugin.o
libtraceevent-y += trace-seq.o
libtraceevent-y += parse-filter.o
libtraceevent-y += parse-utils.o
libtraceevent-y += kbuffer-parse.o

plugin_jbd2-y         += plugin_jbd2.o
plugin_hrtimer-y      += plugin_hrtimer.o
plugin_kmem-y         += plugin_kmem.o
plugin_kvm-y          += plugin_kvm.o
plugin_mac80211-y     += plugin_mac80211.o
plugin_sched_switch-y += plugin_sched_switch.o
plugin_function-y     += plugin_function.o
plugin_xen-y          += plugin_xen.o
plugin_scsi-y         += plugin_scsi.o
plugin_cfg80211-y     += plugin_cfg80211.o
lass='oid'>f598f82e204ec0b17797caaf1b0311c52d43fb9a (patch) tree20e0109db50c168a36df14af76b484eaf9b71836 /include/uapi/mtd/Kbuild parent4180c4c170a5a33b9987b314d248a9d572d89ab0 (diff)
romfs: use different way to generate fsid for BLOCK or MTD
Commit 8a59f5d25265 ("fs/romfs: return f_fsid for statfs(2)") generates a 64bit id from sb->s_bdev->bd_dev. This is only correct when romfs is defined with CONFIG_ROMFS_ON_BLOCK. If romfs is only defined with CONFIG_ROMFS_ON_MTD, sb->s_bdev is NULL, referencing sb->s_bdev->bd_dev will triger an oops. Richard Weinberger points out that when CONFIG_ROMFS_BACKED_BY_BOTH=y, both CONFIG_ROMFS_ON_BLOCK and CONFIG_ROMFS_ON_MTD are defined. Therefore when calling huge_encode_dev() to generate a 64bit id, I use the follow order to choose parameter, - CONFIG_ROMFS_ON_BLOCK defined use sb->s_bdev->bd_dev - CONFIG_ROMFS_ON_BLOCK undefined and CONFIG_ROMFS_ON_MTD defined use sb->s_dev when, - both CONFIG_ROMFS_ON_BLOCK and CONFIG_ROMFS_ON_MTD undefined leave id as 0 When CONFIG_ROMFS_ON_MTD is defined and sb->s_mtd is not NULL, sb->s_dev is set to a device ID generated by MTD_BLOCK_MAJOR and mtd index, otherwise sb->s_dev is 0. This is a try-best effort to generate a uniq file system ID, if all the above conditions are not meet, f_fsid of this romfs instance will be 0. Generally only one romfs can be built on single MTD block device, this method is enough to identify multiple romfs instances in a computer. Link: http://lkml.kernel.org/r/1482928596-115155-1-git-send-email-colyli@suse.de Signed-off-by: Coly Li <colyli@suse.de> Reported-by: Nong Li <nongli1031@gmail.com> Tested-by: Nong Li <nongli1031@gmail.com> Cc: Richard Weinberger <richard.weinberger@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/uapi/mtd/Kbuild')