On 2 April 2018 at 21:29, Tejun Heo wrote:
> Hello, Sitsofe.
>
> Can you see whether the following patch makes any difference?
>
> Thanks.
>
> diff --git a/block/blk-timeout.c b/block/blk-timeout.c
> index a05e367..f0e6e41 100644
> --- a/block/blk-timeout.c
> +++ b/block/blk-timeout.c
> @@ -165,7
Hi Tejun,
On 2 April 2018 at 21:29, Tejun Heo wrote:
>
> Can you see whether the following patch makes any difference?
>
> Thanks.
>
> diff --git a/block/blk-timeout.c b/block/blk-timeout.c
> index a05e367..f0e6e41 100644
> --- a/block/blk-timeout.c
> +++ b/block/blk-timeout.c
> @@ -165,7 +165,7
On 2 April 2018 at 15:33, Jens Axboe wrote:
> On 4/1/18 8:35 AM, Sitsofe Wheeler wrote:
>>
>> While trying to boot an EeePC 900 on the latest git mainline kernel a
>> hang is encountered while systemd is starting services but this did
>> not happen with 4.15. A bisect
Hi,
While trying to boot an EeePC 900 on the latest git mainline kernel a
hang is encountered while systemd is starting services but this did
not happen with 4.15. A bisection narrowed it down to the commit
358f70da49d77c43f2ca11b5da584213b2add29c ("blk-mq: make
blk_abort_request() trigger timeout
On 27 September 2016 at 22:21, Sitsofe Wheeler wrote:
> On 27 September 2016 at 19:36, H. Peter Anvin wrote:
>> On September 27, 2016 3:20:06 AM PDT, Sitsofe Wheeler
>> wrote:
>>>(See http://www.gossamer-threads.com/lists/linux/kernel/2534175 for
>>>the hist
On 5 October 2016 at 22:39, Shaohua Li wrote:
> On Wed, Oct 05, 2016 at 10:31:11PM +0100, Sitsofe Wheeler wrote:
>> On 3 October 2016 at 17:47, Sitsofe Wheeler wrote:
>> >
>> > While trying to do a discard (via blkdiscard --length 1048576
>> > /dev/) to an LVM
On 3 October 2016 at 17:47, Sitsofe Wheeler wrote:
>
> While trying to do a discard (via blkdiscard --length 1048576
> /dev/) to an LVM device atop a two disk md RAID1 the
> following oops was generated:
>
> [ 103.306243] md: resync of RAID array md127
> [ 103.306246] md:
On 5 October 2016 at 16:04, Sitsofe Wheeler wrote:
> On 4 October 2016 at 07:20, Sitsofe Wheeler wrote:
>> On 4 October 2016 at 07:17, Sitsofe Wheeler wrote:
>>> While trying to do a discard inside an ESXi 6 VM to an LVM device atop
>>> an md RAID1 device composed of
On 4 October 2016 at 07:20, Sitsofe Wheeler wrote:
> On 4 October 2016 at 07:17, Sitsofe Wheeler wrote:
>> While trying to do a discard inside an ESXi 6 VM to an LVM device atop
>> an md RAID1 device composed of two SATA SSDs passed up as a raw disk
>> mappings through a PV
On 4 October 2016 at 07:17, Sitsofe Wheeler wrote:
> While trying to do a discard inside an ESXi 6 VM to an LVM device atop
> an md RAID1 device composed of two SATA SSDs passed up as a raw disk
> mappings through a PVSCSI controller, this BUG followed by an Oops was
> hit:
>
While trying to do a discard inside an ESXi 6 VM to an LVM device atop
an md RAID1 device composed of two SATA SSDs passed up as a raw disk
mappings through a PVSCSI controller, this BUG followed by an Oops was
hit:
[ 86.902888] [ cut here ]
[ 86.904600] kernel BUG at a
Hi,
While trying to do a discard (via blkdiscard --length 1048576
/dev/) to an LVM device atop a two disk md RAID1 the
following oops was generated:
[ 103.306243] md: resync of RAID array md127
[ 103.306246] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
[ 103.306248] md: using maximum ava
On 27 September 2016 at 19:36, H. Peter Anvin wrote:
> On September 27, 2016 3:20:06 AM PDT, Sitsofe Wheeler
> wrote:
>>(See http://www.gossamer-threads.com/lists/linux/kernel/2534175 for
>>the history of this thread )
>>
>>On 26 September 2016 at 20:00, Randy Du
(See http://www.gossamer-threads.com/lists/linux/kernel/2534175 for
the history of this thread )
On 26 September 2016 at 20:00, Randy Dunlap wrote:
>
> but the warning in free_init_pages() is about alignment, not size...
> Maybe the concatenation is bad?
What would l have to pull apart to be abl
On 26 September 2016 at 07:47, H. Peter Anvin wrote:
> On September 25, 2016 11:22:04 PM PDT, Sitsofe Wheeler
> wrote:
>>On 26 September 2016 at 03:14, H. Peter Anvin wrote:
>>> On 09/24/16 08:32, Sitsofe Wheeler wrote:
>>>>
>>>> While trying to
On 26 September 2016 at 03:14, H. Peter Anvin wrote:
> On 09/24/16 08:32, Sitsofe Wheeler wrote:
>>
>> While trying to PXE boot a Fedora LiveISO on VMware ESXi the kernel
>> throws the following warning:
>>
> [...]
>>
>> The initrd is big because it ho
Hi,
While trying to PXE boot a Fedora LiveISO on VMware ESXi the kernel
throws the following warning:
[0.955216] Unpacking initramfs...
[5.391977] [ cut here ]
[5.391986] WARNING: CPU: 0 PID: 1 at arch/x86/mm/init.c:671
free_init_pages+0x94/0xa0
[5.391988]
On Wed, Jun 15, 2016 at 06:17:37PM +, Arvind Kumar wrote:
> It is possibly some race. We saw a WRITE SAME related issue in past
> for which Petr sent out a patch but looks like the patch didn't make
> it. :(
>
> https://groups.google.com/forum/#!topic/linux.kernel/1WGDSlyY0y0
Indeed - the inv
On Tue, Jun 07, 2016 at 07:58:25AM -0700, Shaohua Li wrote:
>
> I didn't follow. io_err is only and always set when ret == 0. io_err is
> meanless if ret != 0, because that means the disk doesn't support discard and
> we don't dispatch discard IO. why should we initialized io_err to 0?
My mistake
On Tue, Jun 14, 2016 at 10:14:50PM -0400, Martin K. Petersen wrote:
> > "Christoph" == Christoph Hellwig writes:
>
> Christoph> And I'd much prefer to get this right now. It's not like
> Christoph> this is recently introduced behavior.
>
> Unfortunately there are quite a few callers of blkd
ave
> disk data not changed. zeroout should have guaranteed zero-fill
> behavior.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=118581
>
> V2: move the return value policy to blkdev_issue_discard and
> delete the policy for blkdev_issue_write_same (Martin)
>
> Cc: Sitsofe
On 27 May 2016 at 10:30, Tom Yan wrote:
> There seems to be some sort of race condition between
> blkdev_issue_zeroout() and the scsi disk driver (disabling write same
> after an illegal request). On my UAS drive, sometimes `blkdiscard -z
> /dev/sdX` will return right away, even though if I then c
On Sat, May 28, 2016 at 08:55:43AM +, Sitsofe Wheeler wrote:
> On Thu, May 26, 2016 at 11:08:14AM -0700, Shaohua Li wrote:
> > blkdev_issue_zeroout try discard/writesame first, if they fail, zeroout
> > fallback to regular write. The problem is discard/writesame doesn't
On 27 May 2016 at 05:18, Darrick J. Wong wrote:
>
> It's possible that the pvscsi device advertised WRITE SAME, but if the device
> sends back ILLEGAL REQUEST then the SCSI disk driver will set
> write_same_max_bytes=0. Subsequent BLKZEROOUT attempts will then issue writes
> of zeroes to the driv
Hi,
With Ubuntu's 4.4.0-22-generic kernel and a Fedora 23
4.6.0-1.vanilla.knurd.1.fc23.x86_64 kernel I've found that the
BLKZEROOUT syscall can malfunction and not zero data.
When BLKZEROOUT is issued to an MD device atop a PVSCSI controller
supplied VMDK from ESXi 6.0 the call returns immediatel
CC'ing Jens Axboe.
On 11 February 2016 at 09:54, Jens Rosenboom wrote:
> 2016-02-11 4:48 GMT+01:00 Sitsofe Wheeler :
>> Trying to cc the GNU parted and linux-block mailing lists.
>>
>> On 9 February 2016 at 13:02, Jens Rosenboom wrote:
>>> While trying to
Trying to cc the GNU parted and linux-block mailing lists.
On 9 February 2016 at 13:02, Jens Rosenboom wrote:
> While trying to reproduce some performance issues I have been seeing
> with Ceph, I have come across a strange behaviour which is seemingly
> affected only by the end point (and thereby
On Wed, Dec 10, 2014 at 11:30:30PM +, KY Srinivasan wrote:
>
> > >
> > > + {"Msft", "Virtual Disk", "1.0", BLIST_TRY_VPD_PAGES},
> > >
> > > Is that version field meaningful or is it safe for us to inquire about
> > > VPD pages without problems on older versions?
> >
> > This version is used
On Wed, Dec 10, 2014 at 12:38:25AM -0800, Long Li wrote:
> MSFT targets currently claim SPC-2 compliance while they implement
> post SPC-2 features. With this patch we can correctly handle
> WRITE_SAME_16 issues.
>
> This patch fixes an issue where the flag is setup too late in drive
> initializat
On Mon, Dec 08, 2014 at 06:04:35AM +, KY Srinivasan wrote:
>
> Greg has not committed these patches yet. One of the patches changes the
> balloon floor.
> This means that the guest will not be ballooned down below the floor. Is this
> what you are
> seeing? In our testing we did not see anyt
Hi,
After doing
make-bcache -B /dev/sdf
make-bcache -C /dev/sdh
ls -l /sys/fs/bcache
echo 1110734d-230c-4b8f-a63d-dff472a0977b > /sys/block/bcache0/bcache/attach
the following warnings were produced with a 3.18.0.x86_64-01967-g86c6a2f
kernel:
[ 75.218601] bcache: register_bdev() registered bac
read to post the status.
> This will address the inconsistent lock state that Sitsofe Wheeler
>
> reported:
Sorry I didn't follow up on this. Things looked better after the patch
but I was seeing a strange issue where the memory was being reduced to
some minimum and the balloon
On 11 November 2014 19:27, Long Li wrote:
> It's not obvious if this is a problem with hv_netvsc, or other code.
>
> Can you try to use a legacy network device and see if this issue still exists?
Good point - I'll try that tomorrow (your guess that I was currently
using non-legacy/paravirtualised
While using 3.18.0-rc3.x86_64-00116-g6ac94d3 on a Hyper-V 2012 R2 the
poison in skbuff_fclone_cache was overwritten:
[39099.484435] sd 7:0:0:0: [sdi] Attached SCSI disk
[39099.484688] sd 6:0:0:0: [sdh] Attached SCSI disk
[45285.786640]
=
I've been trying to use the Hyper-V balloon driver to allow the host to
reclaim unused memory but have been hitting issues. With a Hyper-V 2012
R2 guest with 4GBytes of RAM, dynamic memory on, 1GByte minimum 10GByte
maximum, 8 vcpus, running a 3.18.0-rc3 kernel with no swap configured
the following
On 23 October 2014 02:50, Martin K. Petersen wrote:
>>>>>> "Sitsofe" == Sitsofe Wheeler writes:
>
> Sitsofe> 2. On top of the above, when a disk is "small" (has less than
> Sitsofe>2^32 sectors which is typically < 2 TBytes in
On 21 October 2014 18:13, Long Li wrote:
> Thanks Sitsofe. This should have been fixed by this patch:
> http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f88e67149f97d73c704d6fe6f492edde97463025
>
> Can you give it a try?
Ah this one went mainline a few days ago so I've a
On Sun, Oct 12, 2014 at 01:21:01AM +, KY Srinivasan wrote:
>
> > -Original Message-
> > From: Jeff Leung [mailto:jle...@v10networks.ca]
> > Sent: Saturday, October 11, 2014 1:22 PM
> >
> > > On the current release of Windows (windows 10), we are advertising
> > > SPC3 compliance.
> >
On Tue, Oct 14, 2014 at 09:08:28PM -0400, Martin K. Petersen wrote:
> >>>>> "Sitsofe" == Sitsofe Wheeler writes:
>
> Sitsofe> Microsoft Hyper-V virtual disks currently only claim SPC-2
> Sitsofe> compliance causing the kernel skip checks for feature
On Tue, Oct 14, 2014 at 09:06:37PM -0400, Martin K. Petersen wrote:
> >>>>> "Sitsofe" == Sitsofe Wheeler writes:
>
> Sitsofe> A previous patch attempted to add a quirk to workaround this
> Sitsofe> but the quirk was only enabled after the features had
nal Message-
> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On Behalf
> Of Sitsofe Wheeler
> Sent: Thursday, October 09, 2014 6:32 AM
> To: David Miller
> Cc: o...@aepfle.de; net...@vger.kernel.org; jasow...@redhat.com;
> linux-kernel@
impacts Hyper-V's VHD/VHDX virtual disks and not passthrough devices.
Signed-off-by: Sitsofe Wheeler
---
drivers/scsi/scsi_devinfo.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/scsi_devinfo.c b/drivers/scsi/scsi_devinfo.c
index 49014a1..3eadcb1 100644
--- a/drivers
: Sitsofe Wheeler
---
drivers/scsi/scsi_scan.c| 3 +++
drivers/scsi/sd.c | 3 +++
include/scsi/scsi_device.h | 1 +
include/scsi/scsi_devinfo.h | 1 +
4 files changed, 8 insertions(+)
diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
index ba3f1e8..d3f6267 100644
--- a
This reverts commit f3cfabce7a2e92564d380de3aad4b43901fb7ae6 (Drivers:
add blist flags) as it does not enable thin provisioning for my Hyper-V 2012 R2
virtual disks.
Signed-off-by: Sitsofe Wheeler
---
drivers/scsi/storvsc_drv.c | 10 --
1 file changed, 10 deletions(-)
diff --git a
r to only Hyper-V virtual disks and work on small
virtual disks.
Sitsofe Wheeler (3):
Revert "Drivers: add blist flags"
scsi: add try_rc16 blacklist flag
scsi: Use try_rc16 and try_vpd_pages quirks on Hyper-V virtual disks
drivers/scsi/scsi_devinfo.c | 1 +
drivers/scsi/scsi_sc
On Sun, Oct 05, 2014 at 09:11:29PM -0400, David Miller wrote:
> From: "K. Y. Srinivasan"
> Date: Sun, 5 Oct 2014 10:42:51 -0700
>
> > After the packet is successfully sent, we should not touch the packet
> > as it may have been freed. This patch is based on the work done by
> > Long Li .
> >
>
from 0x8100 (relocation range:
0x8000-0x9fff)
---[ end Kernel panic - not syncing: Fatal exception in interrupt
So
Tested-by: Sitsofe Wheeler
But I'm still seeing oopses like the following:
BUG: unable to handle kernel paging request at 8800ec0b9073
IP: [] n
t;
> > -Original Message-
> > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > Sent: Thursday, September 25, 2014 2:08 PM
> >
> > You [Microsoft?] do? Can you link to public sources where is this stated
>
> As far as I know, currently the document abou
On Tue, Sep 23, 2014 at 09:56:10AM +0200, Olaf Hering wrote:
> On Tue, Sep 23, Thomas Shao wrote:
>
> > In current hyper-v time sync service,it only gets the initial clock time
> > from the host. It didn't process the following time samples. This change
> > introduced a module parameter called hos
On Mon, Sep 15, 2014 at 12:25:39PM -0700, Greg Kroah-Hartman wrote:
> 3.14-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: "Martin K. Petersen"
>
> commit c1d40a527e885a40bb9ea6c46a1b1145d42b66a0 upstream.
>
> Despite supporting modern S
On Thu, Sep 04, 2014 at 10:40:14PM -0700, Christoph Hellwig wrote:
> Looks good to me.
>
> Olaf, Hannes - can I get another review for this (and the older hyperv
> scanning patch set)?
I agree this looks useful because on a
59753a805499f1ffbca4ac0a24b3dff67bf1 3.17rc2 kernel with
92578ea Dri
Hello,
On Fri, Aug 29, 2014 at 03:44:20PM +0200, Chloé Desoutter wrote:
>
> [1.] One line summary of the problem:
> On Linux 3.16 a custom-built kernel with bhyve won't boot and will
> hang on the APIC timer calibration.
Wow I haven't seen a report in this style in a while...
> [2.] Full descri
On Fri, Aug 29, 2014 at 05:18:51PM +, KY Srinivasan wrote:
>
> > -Original Message-
> > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > Sent: Friday, August 29, 2014 2:32 AM
> > To: Dexuan Cui
> > Cc: KY Srinivasan; Greg Kro
On Fri, Aug 29, 2014 at 01:24:11PM +0300, Dan Carpenter wrote:
> On Fri, Aug 29, 2014 at 10:16:32AM +, Dexuan Cui wrote:
> >
> > Section 4.11.3 of Hypervisor Top Level Functional Specification(available at
> > http://blogs.msdn.com/b/virtual_pc_guy/archive/2014/02/17/updated-hypervisor-top-lev
While booting a 10 vcpu system with a post v3.17-rc2 kernel with the
"Drivers: hv: vmbus: Eliminate calls to BUG_ON()", "Drivers: hv: vmbus:
Miscellaneous cleanup" patches and debugging/verification config options
on I'm seeing the following:
[ 31.570860] EXT4-fs (sdb1): mounted filesystem with
On Thu, Aug 28, 2014 at 06:29:52PM -0700, K. Y. Srinivasan wrote:
> Minimize failures in this function by pre-allocating the buffer
> for posting messages. The hypercall for posting the message can fail
> for a number of reasons:
>
>
> Cc:
Is this patch useful for all longterm (2.6.32.63, 3.2.
> Drivers: hv: vmbus: Properly protect calls to smp_processor_id()
These patches (on top of the "Drivers: hv: vmbus: Eliminate calls to
BUG_ON()" series) resolve an issue I was seeing where the Hyper-V
framebuffer driver would fail when booting a 3.17.0-rc2 verification
kernel on a UP
us_open()
This patch set resolves a number of BUG_ON crashes I was hitting on
Hyper-V while booting a kernel with verification options on. With these
I can complete a 3.17.0-rc2 boot on an SMP setup although patches from
"Drivers: hv: vmbus: Miscellaneous cleanup" are needed to resolve other
Hi Dexuan,
On Thu, Aug 28, 2014 at 03:21:59AM +, Dexuan Cui wrote:
> > > > First let me thank you guys for looking into this issue. Looking at
Feel free to add
Reported-by: Sitsofe Wheeler
to your patches (it's useful too me because it makes it easier for me to show
what I
On Wed, Aug 27, 2014 at 06:45:55PM +, KY Srinivasan wrote:
>
> > -Original Message-
> > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > Sent: Wednesday, August 27, 2014 9:19 AM
> >
> > > BTW, with the patch below, hyperv_fb ca
On Wed, Aug 27, 2014 at 02:14:02PM +, Dexuan Cui wrote:
> > -Original Message-
> > From: Sitsofe Wheeler
> > Sent: Wednesday, August 27, 2014 20:16 PM
>
> > > I'm making a patch for this.
> Please see the end of the mail for the inline patc
On Wed, Aug 27, 2014 at 11:30:54AM +, Dexuan Cui wrote:
> > -Original Message-
> > From: Sitsofe Wheeler
> > On Tue, Aug 26, 2014 at 10:30:54AM +, Dexuan Cui wrote:
> >
> > > Actually I found the direct cause of the panic: sometimes
&g
On Tue, Aug 26, 2014 at 10:30:54AM +, Dexuan Cui wrote:
> > What is baffles me is the whole UP vs SMP thing - why would UP
> > make this show up consistently? Perhaps some assertions could be added
> > to check that rbi->ring_buffer still has sane values in it after
> > operations on it are f
On Mon, Aug 25, 2014 at 09:48:31PM +, KY Srinivasan wrote:
>
> > There is also a case of the BUG_ON at line 460 being hit (from
> > https://lkml.org/lkml/2014/8/19/708 ):
> >
> > 457ret = vmbus_post_msg(msg,
> > 458 sizeof(struct
> > vmbus_channe
On Tue, Aug 26, 2014 at 12:05:22PM -0700, K. Y. Srinivasan wrote:
> Cleanup the channel management code and eliminate calls to BUG_ON()
>
> K. Y. Srinivasan (4):
> Drivers: hv: vmbus: Cleanup vmbus_post_msg()
> Drivers: hv: vmbus: Cleanup vmbus_teardown_gpadl()
> Drivers: hv: vmbus: Cleanup
On Mon, Aug 25, 2014 at 12:36:48PM +0300, Dan Carpenter wrote:
> The code here is:
>
> drivers/hv/channel.c
>460 BUG_ON(ret != 0);
>461 t = wait_for_completion_timeout(&info->waitevent, 5*HZ);
>462 BUG_ON(t == 0);
>
There is also a case of the BUG_ON at lin
On Tue, Aug 19, 2014 at 12:40:53PM +0100, Sitsofe Wheeler wrote:
> On Tue, Aug 19, 2014 at 10:57:30AM +0200, Daniel Borkmann wrote:
> > On 08/19/2014 10:15 AM, Sitsofe Wheeler wrote:
> > >After a variety of issues on Hyper-V (host is running Windows 2012 R2) I
> > >u
Hi Dexuan,
On Mon, Aug 25, 2014 at 02:02:21PM +, Dexuan Cui wrote:
> > -Original Message-
> > From: Sitsofe Wheeler
> > Sent: Wednesday, August 20, 2014 17:27 PM
> >
> > While booting a Hyper-V 3.17.0-rc1 guest on a 2012 R2 host a BUG was
> > t
Hi,
On Wed, Aug 20, 2014 at 11:15:39AM +, Dexuan Cui wrote:
> > -Original Message-
> > From: Sitsofe Wheeler
> > Sent: Wednesday, August 20, 2014 17:27 PM
> > To: Dexuan Cui
> > Cc: KY Srinivasan; Greg Kroah-Hartman; Haiyang Zhang;
> > de...@
While booting a Hyper-V 3.17.0-rc1 guest on a 2012 R2 host a BUG was
triggered while registering hyperv_fb which in turn caused a panic.
Various kernel debugging options (CONFIG_DEBUG_PAGEALLOC,
CONFIG_SLUB_DEBUG=y...) were on at the time. This only seems to happen
if the guest is being booted with
On Tue, Aug 19, 2014 at 09:29:44PM +, Haiyang Zhang wrote:
>
> > -Original Message-
> > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > Sent: Tuesday, August 19, 2014 8:37 AM
> > To: KY Srinivasan
> > Cc: Greg Kroah-Hartman; Haiyang Zhang; de...@
Now we get to the issue I've been meaning to report: changing the MTU of
a Hyper-V network interface while traffic is flowing through it triggers
a BUG. I've seen this happen on a variety of kernels but the trace below
is from 3.17.0-rc1.
Steps to reproduce:
(Guests were customised Fedora 20 cloud
While booting a Hyper-V 3.17.0-rc1 guest on a 2012 R2 host a BUG was
triggered in drivers/hv/channel.c:504 which in turn caused a panic:
[ 11.367472] Non-volatile memory driver v1.3
[ 11.395587] Linux agpgart interface v0.103
[ 11.425034] loop: module loaded
[ 11.446046] Loading iSCSI tran
On Tue, Aug 19, 2014 at 10:57:30AM +0200, Daniel Borkmann wrote:
> On 08/19/2014 10:15 AM, Sitsofe Wheeler wrote:
> >After a variety of issues on Hyper-V (host is running Windows 2012 R2) I
> >updated to the latest kernel (3.17-rc1
> >7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9),
After a variety of issues on Hyper-V (host is running Windows 2012 R2) I
updated to the latest kernel (3.17-rc1
7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9), turned on a bunch of kernel
validation options and booted which has resulted in a BUG being
triggered (IP claims to be at netvsc_select_queue),
while they implement post SPC-2 features.
> >With this patch we can correctly handle WRITE_SAME_16 issues.
> >
> >Signed-off-by: K. Y. Srinivasan
> >
> Reviewed-by: Hannes Reinecke
On Wed, Jul 23, 2014 at 09:13:41PM +0100, Sitsofe Wheeler wrote:
> On Wed, Jul 23, 2014 a
On Thu, Jul 24, 2014 at 02:09:11PM +, James Bottomley wrote:
> On Thu, 2014-07-24 at 08:56 +0100, Sitsofe Wheeler wrote:
> > Microsoft Hyper-V targets currently only claim SPC-2 compliance / no
> > compliance indicated even though they implement post SPC-2 features
> &
On Thu, Jul 24, 2014 at 08:35:13AM -0700, Christoph Hellwig wrote:
> On Thu, Jul 24, 2014 at 08:34:19AM -0700, Christoph Hellwig wrote:
> > I agree - I'd like to pull in KY's simple fix as soon as I get a second
> > review for it.
>
> Ok, looks like I just got that from Hannes. Let's see if there
On Thu, Jul 24, 2014 at 09:54:24AM -0400, Martin K. Petersen wrote:
> >>>>> "Sitsofe" == Sitsofe Wheeler writes:
>
> Sitsofe> Fix incorrectly named variable. Some block devices (such as
> Sitsofe> Hyper-V passthrough SSDs) support logical block provisi
On Thu, Jul 24, 2014 at 08:47:39AM +0100, Sitsofe Wheeler wrote:
> On Wed, Jul 23, 2014 at 09:13:41PM +0100, Sitsofe Wheeler wrote:
> > On Wed, Jul 23, 2014 at 07:15:58AM -0700, Christoph Hellwig wrote:
> > > On Wed, Jul 23, 2014 at 03:10:28PM +0100, Sitsofe Wheeler wrote:
&g
ng tests.
Signed-off-by: Sitsofe Wheeler
---
drivers/scsi/sd.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index 8249e51..8bf34bc 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi/sd.c
@@ -2559,7 +2559,7 @@ static void sd_read_bloc
Some block devices (such as Hyper-V passthrough SSDs) support logical
block provisioning (e.g. via UNMAP) but don't set lbpme thus disabling
discard. If the try_lbp quirk is in use skip lbpme checks that lead up
to the logical block provisioning tests.
Signed-off-by: Sitsofe Wheeler
---
dr
previous version of this
patch and https://lkml.org/lkml/2014/7/23/615 for example devices.
Original-patch-by: K. Y. Srinivasan
Signed-off-by: Sitsofe Wheeler
---
drivers/scsi/storvsc_drv.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/drivers/scsi/storvsc_drv.c
blacklist flag that allows the forcing of the paths leading
to logical block provisioning tests.
See https://lkml.org/lkml/2014/7/13/59 for the previous version.
Reported-by: K. Y. Srinivasan
Original-patch-by: Martin K. Petersen
Signed-off-by: Sitsofe Wheeler
---
drivers/scsi/scsi_scan.c
On Wed, Jul 23, 2014 at 09:13:41PM +0100, Sitsofe Wheeler wrote:
> On Wed, Jul 23, 2014 at 07:15:58AM -0700, Christoph Hellwig wrote:
> > On Wed, Jul 23, 2014 at 03:10:28PM +0100, Sitsofe Wheeler wrote:
> > > I'm not sure this alone will work - won't sdev_bflags/bf
On Wed, Jul 23, 2014 at 07:15:58AM -0700, Christoph Hellwig wrote:
> On Wed, Jul 23, 2014 at 03:10:28PM +0100, Sitsofe Wheeler wrote:
> > I'm not sure this alone will work - won't sdev_bflags/bflags have
> > already been built at this point?
>
> They've be
On Wed, Jul 23, 2014 at 07:10:14AM -0700, Christoph Hellwig wrote:
> On Wed, Jul 23, 2014 at 01:54:43PM +0100, Sitsofe Wheeler wrote:
> > That's good to know (I was worried the device would not be detected as
> > supporting discard because it doesn't report lb
On Mon, Jul 21, 2014 at 04:06:01PM -0700, K. Y. Srinivasan wrote:
> Add blist flags to permit the reading of the VPD pages even when
> the target may claim SPC-2 compliance. MSFT targets currently
> claim SPC-2 compliance while they implement post SPC-2 features.
> With this patch we can correctly
On Wed, Jul 23, 2014 at 04:51:28AM -0700, Christoph Hellwig wrote:
> On Wed, Jul 23, 2014 at 11:04:48AM +0100, Sitsofe Wheeler wrote:
> > OK I've just seen this as I was about to post a similar patch to get
> > discard going on Hyper-V. Will your patches handle Hyper-V pass
On Mon, Jul 21, 2014 at 04:06:01PM -0700, K. Y. Srinivasan wrote:
> Add blist flags to permit the reading of the VPD pages even when
> the target may claim SPC-2 compliance. MSFT targets currently
> claim SPC-2 compliance while they implement post SPC-2 features.
> With this patch we can correctly
On Mon, Jul 14, 2014 at 10:39:48PM +, Haiyang Zhang wrote:
> > -Original Message-
> > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > Sent: Monday, July 14, 2014 5:31 PM
> > To: Haiyang Zhang
> > Cc: KY Srinivasan; David S. Miller; de...@linuxdri
On Fri, Jul 11, 2014 at 03:25:11PM +, Haiyang Zhang wrote:
>
> > -Original Message-
> > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > Sent: Friday, July 11, 2014 1:53 AM
> > To: Haiyang Zhang
> > Cc: KY Srinivasan; David S. Miller; de...@linux
On Mon, Jul 07, 2014 at 07:13:41PM +0100, Sitsofe Wheeler wrote:
> On Mon, Jul 07, 2014 at 04:54:20PM +, Haiyang Zhang wrote:
> >
> > > -Original Message-
> > > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > > Sent: Sunday, July 6, 2014 4:18
On Mon, Jul 07, 2014 at 04:54:20PM +, Haiyang Zhang wrote:
>
> > -Original Message-
> > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > Sent: Sunday, July 6, 2014 4:18 PM
> > To: Haiyang Zhang
> > Cc: KY Srinivasan; David S. Miller; de...@linux
With the 3.14 kernel Hyper-V no longer reliably enables its networking
devices in time on cloud images leading to network devices permanently
remaining offline.
After a painful round of bisection I've narrowed this down to commit
b679ef73edc251f6d200a7dd2396e9fef9e36fc3 :
# bad: [455c6fdbd219161b
On Wed, Jun 11, 2014 at 11:32:29AM +0200, Daniel Vetter wrote:
> On Wed, Jun 11, 2014 at 07:03:39AM +0100, Sitsofe Wheeler wrote:
> >
> > On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
> > > On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote
On Wed, Jun 11, 2014 at 02:48:46PM +0200, Igor Mammedov wrote:
> On Wed, 11 Jun 2014 07:16:24 +0100
> Sitsofe Wheeler wrote:
>
> > It basically gives up just before Initializing CPU#0. The following is
> > an approximation of the boot messages that I see on the screen (t
On Mon, Jun 09, 2014 at 12:26:16PM +0200, Igor Mammedov wrote:
> On Sun, 8 Jun 2014 10:02:23 +0100
> Sitsofe Wheeler wrote:
>
> > The latest kernel (c593e8978722f7f4a12932733cfeed6c0c74fbaa) refuses to
> > boot on my EeePC - after grub is finished the screen just remains b
(resending because Daniel was dropped from the reply list - I don't know
why)
On Wed, Jun 11, 2014 at 06:46:40AM +0100, Sitsofe Wheeler wrote:
> On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
> > On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote:
>
On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
> On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote:
> > With a tree that is close to 3.15 final I'm regularly seeing the
> > following on my EeePC 900 when starting ioquake3:
> >
> >
1 - 100 of 109 matches
Mail list logo
