[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5293B8B4C8D947B9AA82309DD9A66F53@local.st.by>
Date: Thu, 7 Jun 2012 16:43:24 +0300
From: "Victor Miasnikov" <vvm@....by>
To: "Greg KH" <gregkh@...uxfoundation.org>, <stable@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Cc: "KY Srinivasan" <kys@...rosoft.com>,
"Mike Sterling" <Mike.Sterling@...rosoft.com>
Subject: ToDo: backport to v3.4 , v3.3 , v3.2 patches 1b) db63a4c8115a libata 1) cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default Fw: use hv_storvsc instead of ata_piix for IDE disks ( but not for the CD-ROM)
Hi!
Shortly:
>> Tested ( but, in early implementaition): Ubuntu 12.04 + OpenSUSE
+
I'm test kernel v3.5 on Arch Linux -- all related this patches work Ok
Greg: ( in any case: accept "backport patches" or not) might be very usefull info: what lines from this rules: [. .
.] doesn't meet?
are You read _all_ info/materials [ VVM: sended _later_ Youre first answer ] about problem? See P.S. [ and later in
this e-mail]
==
-- _but_ this is bug in "(drivers_set(ata_piix + hv_storvsc))"
I.e. it is _bug_ in any case
of cource, solution of ( bug in "(drivers_set(ata_piix + hv_storvsc))" ) problem need
"changing the behavior of the ata driver [ VVM: ata_piix ] to accommodate Hyper-V [ VVM: Hyper-V SCSI&ATA driver (
hv_storvsc) ] "
==
---
Full:
{
> > > Hyper-V admins need _worked_ Linux v3.4.X / v3.3.X / v3.2.X
> > > Please, _fix_ errors related "use hv_storvsc instead of ata_piix to
> > > handle the IDE disks devices ( but not for the CD-ROM)"
i.e. need backport to all actual version after 3.1
cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default
and its prerequisite
db63a4c8115a libata: add a host flag to ignore detected ATA devices
}
K.Y.S.> will be nice to have this patch in previous stable releases.
greg k-h > Lots of things would be "nice",
greg k-h > but as this doesn't meet the stable_kernel_rules.txt rules, sorry, I can't take them.
1)
Greg: ( in any case: accept "backport patches" or not) might be very usefull info: what lines from this rules
==
Rules on what kind of patches are accepted, and which ones are not, into the
"-stable" tree:
- It must be obviously correct and tested.
- It cannot be bigger than 100 lines, with context.
- It must fix only one thing.
- It must fix a real bug that bothers people (not a, "This could be a
problem..." type thing).
- It must fix a problem that causes a build error (but not for things
marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
security issue, or some "oh, that's not good" issue. In short, something
critical.
- New device IDs and quirks are also accepted.
- No "theoretical race condition" issues, unless an explanation of how the
race can be exploited is also provided.
- It cannot contain any "trivial" fixes in it (spelling changes,
whitespace cleanups, etc).
- It must follow the Documentation/SubmittingPatches rules.
- It or an equivalent fix must already exist in Linus' tree (upstream).
==
2)
are You read _all_ info/materials about problem? See P.S.
Some additional info:
{
MS > this is not a bug in the ata_piix driver
-- not bug in ata_piix driver itself
-- _but_ this is bug in "(drivers_set(ata_piix + hv_storvsc))"
I.e. it is _bug_ in any case
of cource, solution of ( bug in "(drivers_set(ata_piix + hv_storvsc))" ) problem need
"changing the behavior of the ata driver [ VVM: ata_piix ] to accommodate Hyper-V [ VVM: Hyper-V SCSI&ATA driver (
hv_storvsc) ] "
}
{
----- Original Message -----
From: "Victor Miasnikov"
To: "Greg KH"
Sent: Wednesday, June 06, 2012 7:00 PM
I'm test kernel v3.5 on Arch Linux -- all related this patches work Ok
And {
- It must be obviously correct and tested.
Tested ( but, in early implementaition): Ubuntu 12.04 + OpenSUSE
}
}
Best regards, Victor Miasnikov
Blog: http://vvm.blog.tut.by/
P.S.
History of question:
http://lkml.org/lkml/2012/6/5/23
==
----- Original Message -----
From: "Victor Miasnikov"
To: "Jonathan Nieder"
Sent: Tuesday, June 05, 2012 9:50:16 +0300 AM
. . .
J.N.> {
A workaround is to blacklist the ata_piix module.
However, that means losing access to CD and DVD drives
which are exposed by ata_piix and not hv_storvsc.
}
Yes: work without CD-ROM is not super-fine,
{
best backport patches from v3.5 ( de-facto reincarnation _tested_(!) patches from Ubuntu v12.04 and/or OpenSUSE )
. . .
==
very good description of problem and possible solution:
http://lkml.org/lkml/2012/6/5/6
==
----- Original Message -----
From: "Jonathan Nieder"
To: . . . Cc: . . .
Sent: Tuesday, June 05, 2012 7:59 AM
Subject: Re: [PATCH 2/2] ata_piix: defer disks to the Hyper-V drivers by default
. . .
If I understand correctly,
the problem is that ata_piix and hv_storvsc both claim the (virtual) hard disk.
That sounds worth fixing.
The patch works by making ata_piix skip the disk during enumeration
if hv_storvsc is enabled as a built-in driver or module.
A workaround is to blacklist the ata_piix module.
However, that means losing access to CD and DVD drives
which are exposed by ata_piix and not hv_storvsc.
--
==
http://lkml.org/lkml/2012/6/4/200
==
----- Original Message -----
From: "Victor Miasnikov"
To: _ _ Cc: _ _
Sent: Monday, June 04, 2012 3:33 PM
Subject: Re: Linux on Hyper-V 1) cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default 2) db63a4c8115a
libata: add a host flag to ignore detected ATA device FW: use hv_storvsc instead of ata_piix to handle the IDE disks
devices ( but not for the ...
. . .
patches "does meet the stable_kernel_rules.txt rules" by _all_ criterias . . .
. . .
==
+
==
> + see tranlate from Russian language issue described by Maksim Kramarenko:
> http://lists.debian.org/debian-russian/2012/01/msg00324.html
>> Correct, that is loaded without error, sleep and wake, for a small exception:
>>
>> At the conclusion of the system through the halt or when sending a
>> signal shutdown by ACPI to power down the console fell errors:
>> http://www.k-max.name/wp-content/uploads/2012/01/hyper-v.png
[That image shows the message
exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: failed command: STANDBY IMMEDIATE
]
>> Errors do not interfere with work, but sneaking suspicion about
>> future problems with the hard drive ...
[...]
>> in general, the source of the problem as follows:
>> After [VVM: turn On in kernel source] Hyper-V modules [compile and
>> start use], a hard disk was determined as 2 with the same UUID.
[...]
>> connected to a drive:
>> http://www.k-max.name/wp-content/uploads/2012/01/hdd-e1327750214479.png
>> it is defined as a 2:
>> http://www.k-max.name/wp-content/uploads/2012/01/2hdd.png
>> Naturally, the same UUID:
>> http://www.k-max.name/wp-content/uploads/2012/01/blkid.png
>> That's what tells us the directory / dev:
>> http://www.k-max.name/wp-content/uploads/2012/01/uuid.png
Thanks --- I think this is what Greg was asking for.
==
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists