上海港城危险品仓储有限公司
by hr
中高层管理者的职业化修炼
课程背景
团队管理的本质就是打造一支“招之即来，来之能战，战之能胜的团队”。 “招之即来”是下属忠诚度与上司领导力层面的问题，而“战之能胜”则是能力层面的问题。本课程也是针对如何修炼自我、如何打造团队与如何提高领导力而设置的。
通过《职业心态》的讲述引导学员如何树立正确的职业观念，如何提升主动性、积极性、责任感以及为什么要爱上自己的工作？
通过《企业经营哲学》的讲述，引导学员站在经营者的角度去看待企业管理，站在企业的高度去明确自己的角色和定位。
通过《自我修炼》、《管理修炼》、《领导力提升》、《标准化实施技巧》和《绩效管理与提升技巧》等章节的讲述指引学员如何修炼成为一个德才兼备的职场高手。
本课程的讲师一直在思考解决的一个问题就是如何解决学员“上课听听很激动，课后想想很感动，但随后还是一动不动”的问题，这也是将《思维碰撞》放在第一章节的原因。本章节将引导学员改变观念，保持空杯的心态，并自愿、自发、积极的学习与工作，这个章节的目的是为后面章节的学习效果做铺垫，也是整个课程成功以及课后培训效果转化成功的关键一环。
本课程视角独特，逻辑清晰，案例经典，工具实用，将指引学员进入一个全新的思维世界。
课程简介
培训对象：中高层管理人员、技术、生产、质量管理工程师
授课形式：讲师讲授 + 视频演绎 + 案例研讨 +角色扮演 + 讲师点评 + 落地工具。
课程时间：2天 ( 2016年8月25-26日上海、8月30-31日深圳、9月22-23日北京 、9月28-29日苏州 )
课程费用：3800元/人/2天
咨询方式：05I2-68700652 （0）I80I5596353
课程收益&特点
课程收益1.打开学员心门，引发学员自我反省和深入思考
2.触发学员思维方式的转变
3.激发学员工作和学习的激情、责任感和主动性
4.掌握提升团队配合度、凝聚力、执行力和领导力的技巧
5.掌握标准化和绩效管理提升的设计及实施的技巧
课程特点1.课堂所讲授的工具，大部分来自于世界500强公司使用最广泛、最高效的方法
2.把本期学员最关注问题，作为课堂的实例练习，能够使学员更好的“学以致用”
课程大纲
?第一部分：思维碰撞之意识改变
A: 管理者的挑战
1.管理者最大的挑战是什么？
2.如何改变人做事的结果？
B: 成功和失败的哲学
1.案例分析（失败虽然是成功之母，但过去成功的经验，往往也容易造成今天的失败）
2.你拥有的知识和经验是成就你走到今天的原因，也是让你只走到今天的理由
C：学以致用
1.学会放下与空杯心态
2.学习的四个境界
3.为什么“培训会没有用”？
4.如何做，才能更好的“学以致用”？
D：职业意识转变
1.为什么世界上80%的财富，掌握在20%的人手中？
2.什么是弱者思维？
3.为什么拥有“弱者思维”的人会成为真正的强者？
4.习惯养成之魔法定律：7/21法则
5.新事物接受的三种境界
6.思维修炼的三种境界
7.如何做一个“先知先觉”的人？
?（很多公司举办过多次培训，但培训效果并不是很理想，“学员往往培训时很激动、课后也很感动，但过段时间还是一动不动”，管理者也会因此质疑培训是不是有用？
?如何真正的解决这个困惑，从根本上改变学员的意识与观念，提升培训的长久效果，从而达到最终提升绩效的目的，正是本章节要解决的问题。
?本章节讲述的内容将与学员固化的观念发生激烈的碰撞，并引发学员深入的思考。这部分学习的效果，将影响整个培训过程及培训后实施的效果，也必将奠定学员职业化观念的基础）
?第二部分：自我修炼
A:三项修炼
1.能力提升的三项修炼
2.三项修炼的精彩诠释
3.案例解析（技能是如何修炼而成的）
B:改变命运唯一的机会——学习
1.世界上唯一不变的就是“变”，但比“变”更可怕的是“一成不变”
2.富不学，富不长；穷不学，穷不尽
3.读万卷书，不如名师指路
4.学习最快的方法是什么？
5.学习最高的境界是什么？
C:职业化修炼
1.忠诚与能力孰重孰轻的思考？
2.德才兼备
3.案例分享（道德常常能够弥补智慧的不足，但智慧永远无法填补道德的空白）
4.相随心生（修炼从心开始）
5.职业选手必备的五大能力
6.职业化修炼的六大秘诀
7.修炼的基本逻辑（透过现象看本质，复杂问题简单化，以“道”“驭”“术”）
D：人生反思
1.人活着的目的是什么？
2.让人生变得更有意义的四件事是什么？
3.人生的价值用什么标准去衡量？
4.工作中，怎么做才能让他人和自己都开心？
?（本章节通过《三项修炼》的诠释指引了职业化修炼的方向，通过《修炼的六大秘诀》揭示了修炼的技巧，通过《忠诚与能力》的辩证，揭示了“德才兼备”的深度含义。
?本章节也探寻了一个非常大众而又深奥的问题，即“人为什么活着，如何活的更有意义？”。课程中的精彩的诠释，将令您豁然开朗，并引导您进入全新的思维世界）
?第三部分：企业的经营哲学
A:做事的哲学
1.案例分析（努力一定要在方向正确的情况下，才有机会成功）
2.选择正确的时空，做正确的事情，同时还要正确的做事
3.方向，方法和时空哪一个更重要？
4.管理者的角色认知
B:企业永恒的目标
1.案例分析（战略决定未来）
2.企业追求的永恒目标
3.企业最终的发展会“止于人”
4.案例解析（敬畏和谦卑是智慧的开端）
C:企业管理六要素
1.企业管理六要素
2.案例分析（某上市公司的四五规划解析）
3.案例分析（某上市公司的经营策略解析）
4.华为企业文化之“狼性与做实文化”解析
?（如何选择正确的时空，做正确的事情，同时还能把事情做正确是本章节探讨的一个关键点。
?学员将通过本章节的讲解洞悉管理的哲学、企业管理的六要素、如何站在经营者的角度看待公司管理以及如何站在企业的高度去明确自己的角色与定位）
?第四部分：管理修炼
A:做事最重要的前提
1.做事不由东，累死也无功
2.别人需求和自己需求间的平衡
3.何为素质？
4.若你是老板，你会雇佣现在的你吗？
5.做一个自己满意的人
B:管理修炼
1.管理的经典诠释
2.管理的手段与目的
3.PDCA的经典诠释
?（本章节将引导学员掌握管理修炼的方向和核心技巧）
?领导力提升
A:团队解析
1.团队VS“团伙”
2.为什么一个人是“龙”，一群人就变成 “虫”？
3.如何避免“三个和尚没水吃”的困境？
B:沟通技巧
1.案例解析（你对别人的态度，决定了别人对你的回应）
2.沟通的本质
3.高效沟通的技巧
4.跨部门沟通的技巧
C:领导力提升
1.何为领导？
2.领导力提升的核心技巧
3.三大纪律解析
4.执行力提升之黄金定律：新三大纪律
5.违纪的处理之“征心”原则
6.管理的四境界
7.团队的打造目标
D:主动性提升
1.世界上最遥远的距离是从“头”到“脚”的距离，也就是从“想”到“做”的距离
2.知而未行的原因
3.三省吾身
4.主动性提升的核心技巧
?（何为团队？如何看到沟通的本质？如何进行更好的团队合作？如何管理团队？如何激发团队的凝聚力和执行力？本章节将带着这些问题，指引学员看到管理的本质，并掌握领导力提升的核心技巧。
?培训不仅是要解决“知”的问题，还要解决“行”的问题，如何解决“知易行难”，本章节将给到您满意的答案）
?第五部分：职业心态
A：职业观念
1.“正心、修身、齐家、治国、平天下”给我们带来的启示
2.职业观念
3.保持创新的8条秘诀
B：职场成功的秘诀
1.“变态”和“五心”
2.“赢”的解析
3.如何成为职场赢家？
4.案例分享（因为专注，所以专业）
C：改变从心开始
1.关于改变，值得深思的三句话
2.人生哲学
3.案例解析（One of my days in SH）
4.成功是从爱上你的工作开始（Love what U do）
5.什么样的心态就有什么样的人生
6.如何实现个人、家庭、同事和企业的多赢？
?(本章节将引导学员如何树立正确的职业观念和职业心态，并揭示了职场成功的秘诀是从“爱上自己的工作”开始。
?当一个人成长为职业选手时，也就变成了“招之即来，来之能战，战之能胜”的个人，团队的战斗力也会随之大大增加)
?第六部分：标准化实施技巧
A：标准化的解析
1.“让习惯符合标准，让标准变成习惯”的思考
2.何为标准化？
B：管理之路
1.管理标准化
2.标准表单化
3.表单信息化
4.信息绩效化
C：标准化实施的技巧
1.制定标准的目的
2.目的、目标解析
3.目标设定之SMARTER原则
4.制定标准的原则
5.标准化策划之葵花宝典：MECE
6.MECE的使用技巧
7.MECE的判定标准
8.懒人思维在标准化策划中的应用
9.案例解析（懒人思维的具体应用）
D：标准化的软件工具
1.Mindmanager在流程化、标准化中的应用技巧
2.Visio绘制流程图的技巧
3.Adobe Acrobat在文件整合中的应用技巧
E：流程优化技巧
1.流程优化之SIPOC解析
2.企业运营流程全景图制作实例
3.流程制作实例与技巧
4.表单设计技术
?(标准化是企业基业长青的根本，也是管理者职业化修炼需要掌握的一门技术。本章节将揭示“如何通过制定标准，让不同的人做同样的事，有同样的结果”的方法与技巧。
?“工欲善其事，必先利其器”，本章节将通过MECE、懒人法则、Mindmanager、Visio与Adobe Acrobat等工具的综合应用，使流程优化与标准化的实施过程变成一种享受)
?第七部分：绩效管理与提升技巧
A：管理的核心
1.人之初，“性本善”还是“性本恶”的探索
2.人性解读
3.管理的核心之人性管理
B：绩效考核
1.“做事的哲学源于战争，管理的哲学源于太极”的解析
2.绩效管理四原则
3.为什么大部分的企业绩效考核都以失败告终？
4.企业中绩效考核的终极目标是什么？
5.绩效考核实施的案例分析
6.绩效考核实施中的核心技巧及原则
C：绩效系统构建绩效
1.绩效监控系统构建实例解析
2.绩效数据分析技巧
3.绩效提升的技巧
(“人管人，累死人”，通过什么方式能让员工更主动、积极、自发、持续的努力工作？
站在当下，我们应该告别过去“洗脑式培训”，取而代之的是科学的绩效管理体系。它将通过“绩效管理”这双无形的手推动我们的员工以绩效提升为目的持续的改进，改进，再改进。
如何构建绩效体系，如何进行绩效考核、如何进行绩效提升以及如何规避绩效考核的误区也将是中高层管理者的必修课)
jfyzrf3zjtfy7frmdf51oh0soahchhonjay0rnidteysnstjcs
4 years, 5 months
Re: Subtle races between DAX mmap fault and write path
by Dave Chinner
On Sun, Jul 31, 2016 at 08:13:23PM -0700, Keith Packard wrote:
> Dave Chinner <david(a)fromorbit.com> writes:
>
> > So we'd see that from the point of view of a torn single sector
> > write. Ok, so we better limit DAX to CRC enabled filesystems to
> > ensure these sorts of events are always caught by the filesystem.
>
> Which is the same lack of guarantee that we already get on rotating
> media. Flash media seems to work harder to provide sector atomicity; I
> guess that's a feature?
No, that's not the case. Existing sector based storage guarantees
atomic sector writes - rotating or solid state. I haven't seen one a
corruption caused by a torn sector write in 15 years. BTT layer was
written for pmem to provide this guarantee, but you can't use DAX
through that layer.
In XFS, the only place we really care about torn sector writes in
the journal - we have CRCs there to detect such problems and CRC
enabled filesystems will prevent recovery of checkpoints containing
torn writes. Non-CRC enable filesystems just warn and continue on
their merry way (compatibility reasons - older kernels don't emit
CRCs in log writes), so we really do need to restrict DAX to CRC
enabled filesystems.
> The alternative is to hide metadata behind a translation layer, and
> while that can be done for lame file systems,
No. These "lame" filesystems just need to use their existing
metadata buffering layer to hide this and the journalling subsystem
should protects against torn metadata writes.
> I'd like to see the raw
> hardware capabilities exposed and then make free software that
> constructs a reliable system on top of that.
Not as easy as it sounds. A couple of weeks ago I tried converting
the XFS journal to use DAX to avoid the IO layer and resultant
memcpy(), and I found out that there's a major problem with using
DAX for metadata access on existing filesystems: pmem is not
physically contiguous. I found that out the hard way - the ramdisk
is DAX capable, but each 4k page ithat is allocated to it has a
different memory address.
Filesystems are designed around the fact that the block address
space they are working with is contiguous - that sector N and sector
N+1 can be accessed in the same IO. This is not true for
direct access of pmem - while the sectors might be logically
contiguous, the physical memory that is directly accessed is not.
i.e. when we cross a page boundary, the next page could be on a
different node, on a different device (e.g. RAID0), etc.
Traditional remapping devices (i.e. DM, md, etc) hide the physical
discontiguities from the filesystem - the present a contiguous LBA
and remap/split/combine under the covers where the filesystem is not
aware of it at all.
The reason this is important is that if the filesystem has metadata
constructs larger than a single page it can't use DAX to access them
as a single object because they may lay across a physical
discontiguity in the memory map. Filesystems aren't usually exposed
to this - sectors of a block device are indexed by "Logical Block
Address" for good reason - the LBA address space is supposed to hide
the physical layout of the storage from the layer above the block
device.
OTOH, DAX directly exposes the physical layout to the filesytem.
And because it's DAX-based pmem and not cached struct pages, we
can't run vm_map_ram() to virtually map the range we need to see as
a contiguous range, as we do in XFS for large objects such as directory
blocks and log buffers. For other large objects such as inode
clusters, we can directly map each page as the objects within the
clusters are page aligned and never overlap page boundaries, but
that only works for inode and dquot buffers. Hence DAX as it stands
makes it extremely difficult to "retrofit" DAX into all aspects of
existing fileystems because exposing physical discontiguities breaks
code that assumes they don't exist.
I've been saying this from the start: we can't make use of all the
capabilities of pmem with existing filesystems and DAX. DAX is
supposed to be a *stopgap measure* until pmem native solutions are
built and mature. Finding limitations like the above only serve to
highlight the fact DAX on ext4/XFS is only a partial solution.
The real problem is, as always, a lack of resources to implement
everything we want to be able to do. Building a new filesystem is
hard, takes a long time, and all the people we have that might be
able to do it are fully occupied by maintaining and enhancing the
existing Linux filesystems to support things like DAX or other
functionality that users want (e.g. rmap, reflink, copy offload,
etc).
Cheers,
Dave.
--
Dave Chinner
david(a)fromorbit.com
4 years, 5 months
[BUG] kernel NULL pointer dereference observed during pmem btt switch test
by Yi Zhang
Hello everyone
Could you help check this issue, thanks.
Steps I used:
1. Reserve 4*8G of memory for pmem by add kernel parameter "memmap=8G!4G memmap=8G!12G memmap=8G!20G memmap=8G!28G"
2. Execute below script
#!/bin/bash
pmem_btt_switch() {
sector_size_list="512 520 528 4096 4104 4160 4224"
for sector_size in $sector_size_list; do
ndctl create-namespace -f -e namespace${1}.0 --mode=sector -l $sector_size
ndctl create-namespace -f -e namespace${1}.0 --mode=raw
done
}
for i in 0 1 2 3; do
pmem_btt_switch $i &
done
KERNEL log:
[ 243.404847] nd_pmem namespace2.0: unable to guarantee persistence of writes
[ 243.467271] nd_pmem namespace3.0: unable to guarantee persistence of writes
[ 243.513412] nd_pmem namespace1.0: unable to guarantee persistence of writes
[ 243.544728] nd_pmem namespace0.0: unable to guarantee persistence of writes
[ 243.545371] ------------[ cut here ]------------
[ 243.545381] WARNING: CPU: 10 PID: 2078 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x64/0x80
[ 243.545382] sysfs: cannot create duplicate filename '/devices/virtual/bdi/259:1'
[ 243.545432] Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache sb_edac edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel lrw nd_pmem gf128mul glue_helper ablk_helper cryptd nd_btt hpilo iTCO_wdt iTCO_vendor_support sg hpwdt pcspkr ipmi_ssif ioatdma wmi pcc_cpufreq acpi_cpufreq acpi_power_meter lpc_ich ipmi_si ipmi_msghandler mfd_core shpchp dca nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_multipath ip_tables xfs libcrc32c sd_mod mgag200 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm crc32c_intel tg3 serio_raw hpsa ptp i2c_core scsi_transport_sas pps_core fjes dm_mirror dm_region_hash dm_log dm_mod
[ 243.545435] CPU: 10 PID: 2078 Comm: ndctl Not tainted 4.7.0-rc7 #1
[ 243.545436] Hardware name: HP ProLiant DL580 Gen8, BIOS P79 05/06/2015
[ 243.545439] 0000000000000286 0000000002c04ad5 ffff88006f24f970 ffffffff8134caec
[ 243.545441] ffff88006f24f9c0 0000000000000000 ffff88006f24f9b0 ffffffff8108c351
[ 243.545442] 0000001f0000000c ffff88105d236000 ffff88105d1031e0 ffff8800357427f8
[ 243.545443] Call Trace:
[ 243.545452] [<ffffffff8134caec>] dump_stack+0x63/0x87
[ 243.545460] [<ffffffff8108c351>] __warn+0xd1/0xf0
[ 243.545463] [<ffffffff8108c3cf>] warn_slowpath_fmt+0x5f/0x80
[ 243.545465] [<ffffffff812a0d34>] sysfs_warn_dup+0x64/0x80
[ 243.545466] [<ffffffff812a0e1e>] sysfs_create_dir_ns+0x7e/0x90
[ 243.545469] [<ffffffff8134faaa>] kobject_add_internal+0xaa/0x320
[ 243.545473] [<ffffffff81358d4e>] ? vsnprintf+0x34e/0x4d0
[ 243.545475] [<ffffffff8134ff55>] kobject_add+0x75/0xd0
[ 243.545483] [<ffffffff816e66b2>] ? mutex_lock+0x12/0x2f
[ 243.545489] [<ffffffff8148b0a5>] device_add+0x125/0x610
[ 243.545491] [<ffffffff8148b788>] device_create_groups_vargs+0xd8/0x100
[ 243.545492] [<ffffffff8148b7cc>] device_create_vargs+0x1c/0x20
[ 243.545498] [<ffffffff811b775c>] bdi_register+0x8c/0x180
[ 243.545500] [<ffffffff811b7877>] bdi_register_dev+0x27/0x30
[ 243.545505] [<ffffffff813317f5>] add_disk+0x175/0x4a0
[ 243.545507] [<ffffffff816e66b2>] ? mutex_lock+0x12/0x2f
[ 243.545513] [<ffffffff814afb7f>] ? nvdimm_bus_unlock+0x1f/0x30
[ 243.545518] [<ffffffffa04e039f>] nd_pmem_probe+0x28f/0x360 [nd_pmem]
[ 243.545521] [<ffffffff814b0599>] nvdimm_bus_probe+0x69/0x120
[ 243.545524] [<ffffffff8148e779>] driver_probe_device+0x239/0x460
[ 243.545526] [<ffffffff8148c974>] bind_store+0xd4/0x110
[ 243.545528] [<ffffffff8148c054>] drv_attr_store+0x24/0x30
[ 243.545529] [<ffffffff812a042a>] sysfs_kf_write+0x3a/0x50
[ 243.545531] [<ffffffff8129fa3b>] kernfs_fop_write+0x11b/0x1a0
[ 243.545536] [<ffffffff8121d5e7>] __vfs_write+0x37/0x160
[ 243.545544] [<ffffffff812ceadd>] ? security_file_permission+0x3d/0xc0
[ 243.545550] [<ffffffff810d7e1f>] ? percpu_down_read+0x1f/0x50
[ 243.545552] [<ffffffff8121e8e2>] vfs_write+0xb2/0x1b0
[ 243.545555] [<ffffffff8121fd35>] SyS_write+0x55/0xc0
[ 243.545560] [<ffffffff81003b12>] do_syscall_64+0x62/0x110
[ 243.545563] [<ffffffff816e85e1>] entry_SYSCALL64_slow_path+0x25/0x25
[ 243.545579] ---[ end trace 6d3b90c425a39fda ]---
[ 243.545580] ------------[ cut here ]------------
[ 243.545583] WARNING: CPU: 10 PID: 2078 at lib/kobject.c:240 kobject_add_internal+0x262/0x320
[ 243.545584] kobject_add_internal failed for 259:1 with -EEXIST, don't try to register things with the same name in the same directory.
[ 243.545603] Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache sb_edac edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel lrw nd_pmem gf128mul glue_helper ablk_helper cryptd nd_btt hpilo iTCO_wdt iTCO_vendor_support sg hpwdt pcspkr ipmi_ssif ioatdma wmi pcc_cpufreq acpi_cpufreq acpi_power_meter lpc_ich ipmi_si ipmi_msghandler mfd_core shpchp dca nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_multipath ip_tables xfs libcrc32c sd_mod mgag200 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm crc32c_intel tg3 serio_raw hpsa ptp i2c_core scsi_transport_sas pps_core fjes dm_mirror dm_region_hash dm_log dm_mod
[ 243.545605] CPU: 10 PID: 2078 Comm: ndctl Tainted: G W 4.7.0-rc7 #1
[ 243.545605] Hardware name: HP ProLiant DL580 Gen8, BIOS P79 05/06/2015
[ 243.545607] 0000000000000286 0000000002c04ad5 ffff88006f24f9c0 ffffffff8134caec
[ 243.545608] ffff88006f24fa10 0000000000000000 ffff88006f24fa00 ffffffff8108c351
[ 243.545610] 000000f06f24fa28 ffff880035164010 ffff88006c7e3780 00000000ffffffef
[ 243.545610] Call Trace:
[ 243.545612] [<ffffffff8134caec>] dump_stack+0x63/0x87
[ 243.545614] [<ffffffff8108c351>] __warn+0xd1/0xf0
[ 243.545616] [<ffffffff8108c3cf>] warn_slowpath_fmt+0x5f/0x80
[ 243.545618] [<ffffffff812a0d3c>] ? sysfs_warn_dup+0x6c/0x80
[ 243.545619] [<ffffffff8134fc62>] kobject_add_internal+0x262/0x320
[ 243.545621] [<ffffffff81358d4e>] ? vsnprintf+0x34e/0x4d0
[ 243.545622] [<ffffffff8134ff55>] kobject_add+0x75/0xd0
[ 243.545625] [<ffffffff816e66b2>] ? mutex_lock+0x12/0x2f
[ 243.545626] [<ffffffff8148b0a5>] device_add+0x125/0x610
[ 243.545628] [<ffffffff8148b788>] device_create_groups_vargs+0xd8/0x100
[ 243.545630] [<ffffffff8148b7cc>] device_create_vargs+0x1c/0x20
[ 243.545632] [<ffffffff811b775c>] bdi_register+0x8c/0x180
[ 243.545634] [<ffffffff811b7877>] bdi_register_dev+0x27/0x30
[ 243.545636] [<ffffffff813317f5>] add_disk+0x175/0x4a0
[ 243.545638] [<ffffffff816e66b2>] ? mutex_lock+0x12/0x2f
[ 243.545640] [<ffffffff814afb7f>] ? nvdimm_bus_unlock+0x1f/0x30
[ 243.545642] [<ffffffffa04e039f>] nd_pmem_probe+0x28f/0x360 [nd_pmem]
[ 243.545644] [<ffffffff814b0599>] nvdimm_bus_probe+0x69/0x120
[ 243.545646] [<ffffffff8148e779>] driver_probe_device+0x239/0x460
[ 243.545648] [<ffffffff8148c974>] bind_store+0xd4/0x110
[ 243.545649] [<ffffffff8148c054>] drv_attr_store+0x24/0x30
[ 243.545651] [<ffffffff812a042a>] sysfs_kf_write+0x3a/0x50
[ 243.545652] [<ffffffff8129fa3b>] kernfs_fop_write+0x11b/0x1a0
[ 243.545654] [<ffffffff8121d5e7>] __vfs_write+0x37/0x160
[ 243.545657] [<ffffffff812ceadd>] ? security_file_permission+0x3d/0xc0
[ 243.545659] [<ffffffff810d7e1f>] ? percpu_down_read+0x1f/0x50
[ 243.545661] [<ffffffff8121e8e2>] vfs_write+0xb2/0x1b0
[ 243.545663] [<ffffffff8121fd35>] SyS_write+0x55/0xc0
[ 243.545665] [<ffffffff81003b12>] do_syscall_64+0x62/0x110
[ 243.545666] [<ffffffff816e85e1>] entry_SYSCALL64_slow_path+0x25/0x25
[ 243.545667] ---[ end trace 6d3b90c425a39fdb ]---
[ 243.577109] BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
[ 243.577117] IP: [<ffffffff812a1054>] sysfs_do_create_link_sd.isra.2+0x34/0xb0
[ 243.577119] PGD 1057752067 PUD 105e37a067 PMD 0
[ 243.577121] Oops: 0000 [#1] SMP
[ 243.577154] Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache sb_edac edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel lrw nd_pmem gf128mul glue_helper ablk_helper cryptd nd_btt hpilo iTCO_wdt iTCO_vendor_support sg hpwdt pcspkr ipmi_ssif ioatdma wmi pcc_cpufreq acpi_cpufreq acpi_power_meter lpc_ich ipmi_si ipmi_msghandler mfd_core shpchp dca nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_multipath ip_tables xfs libcrc32c sd_mod mgag200 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm crc32c_intel tg3 serio_raw hpsa ptp i2c_core scsi_transport_sas pps_core fjes dm_mirror dm_region_hash dm_log dm_mod
[ 243.577157] CPU: 6 PID: 2078 Comm: ndctl Tainted: G W 4.7.0-rc7 #1
[ 243.577158] Hardware name: HP ProLiant DL580 Gen8, BIOS P79 05/06/2015
[ 243.577159] task: ffff8800340c8000 ti: ffff88006f24c000 task.ti: ffff88006f24c000
[ 243.577162] RIP: 0010:[<ffffffff812a1054>] [<ffffffff812a1054>] sysfs_do_create_link_sd.isra.2+0x34/0xb0
[ 243.577163] RSP: 0018:ffff88006f24fc28 EFLAGS: 00010246
[ 243.577164] RAX: 0000000000000000 RBX: 0000000000000040 RCX: 0000000000000001
[ 243.577164] RDX: 0000000000000001 RSI: 0000000000000040 RDI: ffffffff822411f0
[ 243.577165] RBP: ffff88006f24fc50 R08: ffff8800690f1711 R09: ffffffff8134e82e
[ 243.577166] R10: ffff88007799b640 R11: ffffea0000d46000 R12: ffffffff81a3dc3c
[ 243.577166] R13: ffff88105ae627f8 R14: 0000000000000001 R15: ffff880034a89040
[ 243.577168] FS: 00007f685b5dc780(0000) GS:ffff880077980000(0000) knlGS:0000000000000000
[ 243.577168] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 243.577169] CR2: 0000000000000040 CR3: 000000105bb0b000 CR4: 00000000001406e0
[ 243.577170] Stack:
[ 243.577172] ffff880070666000 ffff880070666080 ffff88006a0635d0 ffff88007066600c
[ 243.577173] ffff880034a89040 ffff88006f24fc60 ffffffff812a10f5 ffff88006f24fcc8
[ 243.577175] ffffffff8133188b ffff880070666000 1030000135282c00 ffff880070666000
[ 243.577175] Call Trace:
[ 243.577179] [<ffffffff812a10f5>] sysfs_create_link+0x25/0x40
[ 243.577184] [<ffffffff8133188b>] add_disk+0x20b/0x4a0
[ 243.577189] [<ffffffffa04e039f>] nd_pmem_probe+0x28f/0x360 [nd_pmem]
[ 243.577194] [<ffffffff814b0599>] nvdimm_bus_probe+0x69/0x120
[ 243.577198] [<ffffffff8148e779>] driver_probe_device+0x239/0x460
[ 243.577200] [<ffffffff8148c974>] bind_store+0xd4/0x110
[ 243.577202] [<ffffffff8148c054>] drv_attr_store+0x24/0x30
[ 243.577203] [<ffffffff812a042a>] sysfs_kf_write+0x3a/0x50
[ 243.577205] [<ffffffff8129fa3b>] kernfs_fop_write+0x11b/0x1a0
[ 243.577209] [<ffffffff8121d5e7>] __vfs_write+0x37/0x160
[ 243.577215] [<ffffffff812ceadd>] ? security_file_permission+0x3d/0xc0
[ 243.577220] [<ffffffff810d7e1f>] ? percpu_down_read+0x1f/0x50
[ 243.577222] [<ffffffff8121e8e2>] vfs_write+0xb2/0x1b0
[ 243.577224] [<ffffffff8121fd35>] SyS_write+0x55/0xc0
[ 243.577229] [<ffffffff81003b12>] do_syscall_64+0x62/0x110
[ 243.577232] [<ffffffff816e85e1>] entry_SYSCALL64_slow_path+0x25/0x25
[ 243.577248] Code: 48 89 e5 41 57 41 56 41 55 41 54 49 89 d4 53 74 73 48 85 ff 49 89 fd 74 6b 48 89 f3 48 c7 c7 f0 11 24 82 41 89 ce e8 7c 72 44 00 <48> 8b 1b 48 85 db 74 08 48 89 df e8 ac c1 ff ff 48 c7 c7 f0 11
[ 243.577250] RIP [<ffffffff812a1054>] sysfs_do_create_link_sd.isra.2+0x34/0xb0
[ 243.577251] RSP <ffff88006f24fc28>
[ 243.577251] CR2: 0000000000000040
[ 243.577285] ---[ end trace 6d3b90c425a39fdc ]---
[ 243.578932] Kernel panic - not syncing: Fatal exception
[ 243.597839] Kernel Offset: disabled
[ 247.934728] ---[ end Kernel panic - not syncing: Fatal exception
Best Regards,
Yi Zhang
4 years, 5 months