From: Laurent Vivier <lvivier@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, Akihiko Odaki <akihiko.odaki@daynix.com>,
Sriram Yagnaraman <sriram.yagnaraman@est.tech>,
Dmitry Fleytman <dmitry.fleytman@gmail.com>
Subject: Re: [PATCH v2 2/2] e1000e: fix link state on resume
Date: Tue, 5 Mar 2024 11:06:57 +0100 [thread overview]
Message-ID: <622dabbe-a215-476a-b72c-41d1103b7cb6@redhat.com> (raw)
In-Reply-To: <CACGkMEtzqCA_x1hg-ddp0d-Q-+XLH01k2Pf0KziiYSeLmDwaXA@mail.gmail.com>
On 2/1/24 06:45, Jason Wang wrote:
> On Wed, Jan 24, 2024 at 6:40 PM Laurent Vivier <lvivier@redhat.com> wrote:
>>
>> On resume e1000e_vm_state_change() always calls e1000e_autoneg_resume()
>> that sets link_down to false, and thus activates the link even
>> if we have disabled it.
>>
>> The problem can be reproduced starting qemu in paused state (-S) and
>> then set the link to down. When we resume the machine the link appears
>> to be up.
>>
>> Reproducer:
>>
>> # qemu-system-x86_64 ... -device e1000e,netdev=netdev0,id=net0 -S
>>
>> {"execute": "qmp_capabilities" }
>> {"execute": "set_link", "arguments": {"name": "net0", "up": false}}
>> {"execute": "cont" }
>>
>> To fix the problem, merge the content of e1000e_vm_state_change()
>> into e1000e_core_post_load() as e1000 does.
>>
>> Buglink: https://issues.redhat.com/browse/RHEL-21867
>> Fixes: 6f3fbe4ed06a ("net: Introduce e1000e device emulation")
>> Suggested-by: Akihiko Odaki <akihiko.odaki@daynix.com>
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> ---
>>
>
> I've queued this.
Ping?
Thanks,
Laurent
next prev parent reply other threads:[~2024-03-05 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 10:40 [PATCH v2 2/2] e1000e: fix link state on resume Laurent Vivier
2024-01-28 11:37 ` Akihiko Odaki
2024-02-01 5:45 ` Jason Wang
2024-03-05 10:06 ` Laurent Vivier [this message]
2024-03-06 5:29 ` Jason Wang
2024-03-08 8:09 ` Jason Wang
2024-03-08 8:21 ` Laurent Vivier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=622dabbe-a215-476a-b72c-41d1103b7cb6@redhat.com \
--to=lvivier@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=dmitry.fleytman@gmail.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sriram.yagnaraman@est.tech \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).