From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
To: rrs@researchut.com, linux-um@lists.infradead.org
Subject: Re: uml segfault during I/O
Date: Thu, 17 Oct 2019 14:33:13 +0100 [thread overview]
Message-ID: <cf1294b2-e1cc-961c-e8e1-d070fe0ea94d@cambridgegreys.com> (raw)
In-Reply-To: <5dc5e0694d2fcf2f8bb083e3861fd1b39c768b8c.camel@researchut.com>
On 17/10/2019 14:30, Ritesh Raj Sarraf wrote:
> On Thu, 2019-10-17 at 14:02 +0100, Anton Ivanov wrote:
>> Looking into that. I have not run into anything like that, but I have
>> not used any of the legacy networking for 5 odd years now.
>>
>
> Do you think this is related to networking ? I ask because there was no
> network activity going on.
no, it's disk somewhere. I managed to reproduce it with 5.2 stock on
Debian 5.2 host.
>
> apt is just an example. The packages were all already downloaded and
> there was no network activity. Rather, there was block I/O.
I am looking into that.
>
> One thing I noticed, which may or may not be useful to this report. I
> was booting the uml guest and immediately logging into it and running
> the block I/O. And the segfault would occur.
>
> If I, instead, booted the uml vm and let it remain idle for a minute or
> so and then did the I/O, it worked fine. So I am not sure if there is
> any lazy initialization happening in the background which gets
> corrupted during immediate hot boot I/O.
Interesting...
>
> On the other hand, if you think there can be any number of commands to
> run locally that could generate more information, please assist me so.
As I said - I managed to reproduce it, I am looking at it. In first
instance I am trying with a couple of version up/down to see if this is
5.2 specific.
>
> Thanks,
> Ritesh
>
>
> _______________________________________________
> linux-um mailing list
> linux-um@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-um
>
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2019-10-17 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 11:37 uml segfault during I/O Ritesh Raj Sarraf
[not found] ` <1ccf27d8-6b6a-7d08-acef-93077f07511b@cambridgegreys.com>
2019-10-17 13:30 ` Ritesh Raj Sarraf
2019-10-17 13:33 ` Anton Ivanov [this message]
2019-10-17 15:03 ` Anton Ivanov
2019-10-17 16:29 ` Anton Ivanov
2019-10-18 7:35 ` Anton Ivanov
2019-10-18 8:57 ` Johannes Berg
2019-10-18 9:13 ` Anton Ivanov
2019-10-18 9:49 ` Anton Ivanov
2019-10-18 9:55 ` Anton Ivanov
2019-10-18 10:51 ` Anton Ivanov
2019-10-28 16:51 ` Anton Ivanov
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=cf1294b2-e1cc-961c-e8e1-d070fe0ea94d@cambridgegreys.com \
--to=anton.ivanov@cambridgegreys.com \
--cc=linux-um@lists.infradead.org \
--cc=rrs@researchut.com \
/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