[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system
From: |
Fam Zheng |
Subject: |
Re: [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system |
Date: |
Fri, 27 Jul 2018 20:17:37 +0800 |
On Fri, Jul 27, 2018 at 6:04 PM Kevin Wolf <address@hidden> wrote:
>
> Am 27.07.2018 um 11:24 hat Fam Zheng geschrieben:
> > On Tue, 07/24 16:47, Fam Zheng wrote:
> > > Something has locked /dev/null on my system (I still don't know what to
> > > do with
> > > the annoying incapability of lslocks, or more precisely /proc/locks, on
> > > inspecting OFD lock information), and as a result 226 cannot pass due to
> > > the
> > > unexpected image locking error.
> > >
> > > Fix the test case by disabling locking, and add a doc text about using
> > > test
> > > images.
> > >
> > > Fam Zheng (2):
> > > docs: Describe using images in writing iotests
> > > iotests: Don't lock /dev/null in 226
> > >
> > > docs/devel/testing.rst | 11 +++++++++++
> > > tests/qemu-iotests/226 | 4 ++--
> > > 2 files changed, 13 insertions(+), 2 deletions(-)
> >
> > Kevin, could you apply this for 3.0 too?
>
> Sure, applied to the block branch.
>
> Out of curiosity, did you find out what had locked the devices?
No, but I'll for sure allocate some time to understand kernel's OFD
internals, find the holder application, then hopefully, propose
something that can fix lslocks.
Thanks,
Fam
>
> Kevin
- [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system, Fam Zheng, 2018/07/24
- [Qemu-devel] [PATCH 1/2] docs: Describe using images in writing iotests, Fam Zheng, 2018/07/24
- [Qemu-devel] [PATCH 2/2] iotests: Don't lock /dev/null in 226, Fam Zheng, 2018/07/24
- Re: [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system, Eric Blake, 2018/07/24
- Re: [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system, John Snow, 2018/07/24
- Re: [Qemu-devel] [PATCH 0/2] iotests: Fix 226 on _my_ system, Fam Zheng, 2018/07/27