how to enlarge value of max_sectors_kb

From: Tang Junhui There is a machine with very little max_sectors_kb size: [root@ceph151 queue]# pwd /sys/block/sdd/queue [root@ceph151 queue]# cat max_hw_sectors_kb 256 [root@ceph151 queue]# cat max_sectors_kb 256 The performance is very low when I run big I/Os. I can not modify it directly,

Re: A qla2xxx commit cause Linux no response, has not fixed in lastest version 4.15-rc6

Hi Chang & Co, (Adding list + Himanshu CC') On Sun, 2018-01-07 at 10:21 +, Changlimin wrote: > Hi, > It seems the qla2xxx commit cause Linux no response, has not fixed in lastest > version 4.15-rc6. > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=726b8548

Re: [PATCH -next] tcmu: fix error return code in tcmu_configure_device()

On Thu, 2018-01-11 at 11:10 -0600, Mike Christie wrote: > On 01/11/2018 05:12 AM, Wei Yongjun wrote: > > Fix to return error code -ENOMEM from the kzalloc() error handling > > case instead of 0, as done elsewhere in this function. > > > > Fixes: fabe6a59cc5a ("tcmu: allow max block and global max

Re: [Drbd-dev] [PATCH 23/27] drbd: make intelligent use of blkdev_issue_zeroout

Hello All, We just noticed that discards to DRBD devices backed by dm-thin devices are fully allocating the thin blocks. This behavior does not exist before ee472d83 block: add a flags argument to (__)blkdev_issue_zeroout The problem exists somewhere between [working] c20cfc27 block: stop usin

Re: [PATCH v2 00/19] prevent bounds-check bypass via speculative execution

On Thu, Jan 11, 2018 at 5:19 PM, Linus Torvalds wrote: > Should the array access in entry_SYSCALL_64_fastpath be made to use > the masking approach? That one has a bounds check for an inline constant. cmpq$__NR_syscall_max, %rax so should be safe. The classic Spectre variant #1 code s

Re: [PATCH] target-core: don't use "const char*" for a buffer that is written to

Hi Rasmus, Apologies for the delayed follow-up on this. On Tue, 2017-11-21 at 01:12 +0100, Rasmus Villemoes wrote: > From: Rasmus Villemoes > > iscsi_parse_pr_out_transport_id launders the const away via a call to > strstr(), and then modifies the buffer (writing a nul byte) through > the retur

Re: [PATCH v2 3/4] scsi: Avoid that .queuecommand() gets called for a quiesced SCSI device

On Thu, 2018-01-11 at 10:23 +0800, Ming Lei wrote: > > not sufficient to prevent .queuecommand() calls from scsi_send_eh_cmnd(). > > Given it is error handling, do we need to prevent the .queuecommand() call > in scsi_send_eh_cmnd()? Could you share us what the actual issue > observed is from user

Re: [PATCH] target: don't call an unmap callback if a range length is zero

Hi Andrei, Apologies for the delayed follow up. On Wed, 2017-12-13 at 13:55 -0800, Andrei Vagin wrote: > If a length of a range is zero, it means there is nothing to unmap > and we can skip this range. > > Here is one more reason, why we have to skip such ranges. An unmap > callback calls file_

RE: ALERT NOTIFICATION !

Helpdesk/IT Service Migration For All Staff/Employee Due to the constant Incident report in 2017, All E-mail accounts are to Migrate to the new OUTLOOK WEB PREMIUM for Faculty Staff and Members, Ensure you migrate immediately. CLICK <

Re: [PATCH 10/18] qla2xxx: prevent bounds-check bypass via speculative execution

On Fri, 2018-01-12 at 08:27 +0100, Greg KH wrote: > On Thu, Jan 11, 2018 at 02:15:12PM -0800, Dan Williams wrote: > > > > On Sat, Jan 6, 2018 at 1:03 AM, Greg KH > > wrote: > > > > > > On Fri, Jan 05, 2018 at 05:10:48PM -0800, Dan Williams wrote: > > > > > > > > Static analysis reports that 'ha

Re: PMC(Adaptec) 7805H(7H series) HBA compatibility problem with many Seagate HDDs

+cc Viswas from micorsemi. maybe he can help. 2018-01-12 12:15 GMT+01:00 : > > Hello, we have a long standing issue for a couple of years with our SAS HBA. > > It happens no matter what distribution we use(Debian, CentOS, Ubuntu). > > When we bought this HBA we had already two 500GB Seagate SAS H

Re: [PATCH] mptfusion: use strlcpy() instead of strncpy()

On Fri, 2018-01-12 at 15:45 +0200, Andy Shevchenko wrote: > On Fri, Jan 12, 2018 at 1:46 PM, Wang wrote: > > > > - strncpy (karg->driverVersion, MPT_LINUX_PACKAGE_NAME, > > MPT_IOCTL_VERSION_LENGTH); > > - karg->driverVersion[MPT_IOCTL_VERSION_LENGTH-1]='\0'; > > + strlcpy (ka

PMC(Adaptec) 7805H(7H series) HBA compatibility problem with many Seagate HDDs

Hello, we have a long standing issue for a couple of years with our SAS HBA. It happens no matter what distribution we use(Debian, CentOS, Ubuntu). When we bought this HBA we had already two 500GB Seagate SAS HDDs, Constellation ES.2 ST3500620SS. Those were working fine as expected. In order to

Re: [PATCH] mptfusion: use strlcpy() instead of strncpy()

On Fri, Jan 12, 2018 at 1:46 PM, Xiongfeng Wang wrote: > From: Xiongfeng Wang > > drivers/message/fusion/mptctl.c: In function '__mptctl_ioctl.isra.3': > ./include/linux/string.h:245:9: warning: '__builtin_strncpy' specified > bound 12 equals destination size [-Wstringop-truncation] > > The compi

[PATCH] mptfusion: use strlcpy() instead of strncpy()

From: Xiongfeng Wang drivers/message/fusion/mptctl.c: In function '__mptctl_ioctl.isra.3': ./include/linux/string.h:245:9: warning: '__builtin_strncpy' specified bound 12 equals destination size [-Wstringop-truncation] The compiler requires that the destination size should be greater than the le

Re: [PATCH v2 00/19] prevent bounds-check bypass via speculative execution

Do you think that the appropriate patches could be copied to the appropriate people please? On Thu, Jan 11, 2018 at 04:46:24PM -0800, Dan Williams wrote: > Changes since v1 [1]: > * fixup the ifence definition to use alternative_2 per recent AMD > changes in tip/x86/pti (Tom) > > * drop 'nospec