- 02 Mar, 2016 40 commits
-
-
Andreas Dilger authored
Fixup the MODULE_DESCRIPTION for several lustre modules. Some wrongly place the version in the string or they are not descriptive enough. Broken out of patch http://review.whamcloud.com/16787. Signed-off-by:
Andreas Dilger <andreas.dilger@intel.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6204 Reviewed-on: http://review.whamcloud.com/16787Reviewed-by:
John L. Hammond <john.hammond@intel.com> Reviewed-by:
Dmitry Eremin <dmitry.eremin@intel.com> Reviewed-by:
Frank Zago <fzago@cray.com> Reviewed-by:
Oleg Drokin <oleg.drokin@intel.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
James Simmons authored
For several lustre modules the MODULE_VERSION has the wrong value, located in the wrong place in the source code, or completely missing. This patch brings it up to date. Signed-off-by:
James Simmons <uja.ornl@yahoo.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6204 Reviewed-on: http://review.whamcloud.com/16729Reviewed-by:
-
Andreas Dilger authored
For LNet selftest module the MODULE_AUTHOR was missing. Add proper OpenSFS authorship. Broken out of patch http://review.whamcloud.com/16787. Signed-off-by:
-
James Simmons authored
Move the MODULE_* field in module.c that belongs to libcfs to the end of the file like it is done for other kernel drivers. Signed-off-by:
James Simmons <jsimmons@infradead.org> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
Amitoj Kaur Chawla <amitoj1606@gmail.com> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Amitoj Kaur Chawla authored
Use kmem_cache_zalloc instead of manually setting kmem_cache_alloc with flag GFP_ZERO since kmem_alloc_zalloc sets allocated memory to zero. The Coccinelle semantic patch used to make this change is as follows: // <smpl> @@ expression e,f; @@ - kmem_cache_alloc(e, f |__GFP_ZERO) + kmem_cache_zalloc(e, f) // </smpl> Signed-off-by:
-
Oleg Drokin authored
As it is ENABLE_PINGER is never defined, but in reality it's the code that is now compiled out that should be used since all other instances were converted like that too. Signed-off-by:
Oleg Drokin <green@linuxhacker.ru> Signed-off-by:
-
Oleg Drokin authored
Since there's only one call in those if () else branches, the braces are not really necessary. Highlighted by checkpatch. Signed-off-by:
-
Oleg Drokin authored
KMALLOC_MAX_SIZE is always defined in the kernel, so no point in checking for it, just use t directly. Signed-off-by:
-
Oleg Drokin authored
Found with checkpatch. Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
Signed-off-by:
-
Oleg Drokin authored
Not used in the kernel proper. Signed-off-by:
-
Oleg Drokin authored
Signed-off-by:
-
Oleg Drokin authored
Remove the ifdefs for the around usage. Signed-off-by:
-
Oleg Drokin authored
The new DNE code does not use them either so they are not longer needed. Signed-off-by:
-
Oleg Drokin authored
Since liblustre is no longer with us, referencing to it in the explanations only makes things less clear Signed-off-by:
-
Oleg Drokin authored
These two comments certainly refer to some ifdefed code that is no longer present, so remove them too. Signed-off-by:
-
Oleg Drokin authored
The only caller was not looking at the return value, and liblustre, that cared about it is not part of the kernel client. Signed-off-by:
-
Oleg Drokin authored
And also struct lustre_rw_params that is only referenced by it. Signed-off-by:
-
Oleg Drokin authored
liblustre_check_services is no longer present in the tree. Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" and "space prohibited between function name and open parenthesis" Signed-off-by:
-
Oleg Drokin authored
This mostly fixes checkpatch complaints about "Alignment should match open parenthesis" Signed-off-by:
-
Randy Dunlap authored
Fix build errors by limiting UNISYS_VISORINPUT to the INPUT kconfig setting. drivers/built-in.o: In function `visorinput_remove': visorinput.c:(.text+0x20802e): undefined reference to `input_unregister_device' drivers/built-in.o: In function `visorinput_probe': visorinput.c:(.text+0x208177): undefined reference to `input_allocate_device' visorinput.c:(.text+0x208241): undefined reference to `input_register_device' visorinput.c:(.text+0x20824d): undefined reference to `input_free_device' visorinput.c:(.text+0x208286): undefined reference to `input_allocate_device' visorinput.c:(.text+0x208302): undefined reference to `input_set_abs_params' visorinput.c:(.text+0x20831a): undefined reference to `input_set_abs_params' visorinput.c:(.text+0x20833f): undefined reference to `input_register_device' visorinput.c:(.text+0x20834b): undefined reference to `input_free_device' visorinput.c:(.text+0x20835f): undefined reference to `input_set_capability' drivers/built-in.o: In function `visorinput_channel_interrupt': visorinput.c:(.text+0x20851e): undefined reference to `input_event' visorinput.c:(.text+0x20862c): undefined reference to `input_event' drivers/built-in.o: In function `input_report_key': visorinput.c:(.text+0x207fd1): undefined reference to `input_event' drivers/built-in.o: In function `input_sync': visorinput.c:(.text+0x207fdc): undefined reference to `input_event' Signed-off-by:
Randy Dunlap <rdunlap@infradead.org> Signed-off-by:
-
Tim Sell authored
This patch saves off the create_bus and create_device controlvm messages for the visorhba device, so that they can be resurrected and used in the kdump kernel. After this patch, a crash dump can be generated using: # service kdump start # echo 1 > /proc/sys/kernel/sysrq # echo c > /proc/sysrq-trigger Signed-off-by:Timothy Sell <timothy.sell@unisys.com> Signed-off-by:
David Kershner <david.kershner@unisys.com> Signed-off-by:
-
Tim Sell authored
Use the dynamic size of the controlvm channel (struct channel_header.size) instead of the statically computed sizeof(struct controlvm_channel) when determining the valid bounds for visorchannel_read() and visorchannel_write(). This prevents an observed problem where kdump was failing because controlvm_channel.local_crash_msg_offset was pointing beyond the statically computed size of the channel, even though the channel was physically large enough. This was causing visorchannel_read() to unecessarily fail, because we thought we were attempting to access memory outside of the channel. Signed-off-by:
-
