All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: anton.ivanov@kot-begemot.co.uk,
	user-mode-linux-devel@lists.sourceforge.net
Cc: Daniel Walter <dwalter@google.com>
Subject: Re: [uml-devel] [PATCH] Fix for "occasional userspace process in D/Z state" bug
Date: Fri, 26 Sep 2014 13:56:44 +0200	[thread overview]
Message-ID: <5425547C.1080002@nod.at> (raw)
In-Reply-To: <1411732166-653849-1-git-send-email-anton.ivanov@kot-begemot.co.uk>

Am 26.09.2014 13:49, schrieb anton.ivanov@kot-begemot.co.uk:
> From: Anton Ivanov <antivano@cisco.com>
> 
> This is a fix for a very old UML bug which can be triggered with stock 
> UML. It takes a lot of effort to trigger it there because the 
> lseek()/read() | write() mechanics of the UBD driver implicitly sync the 
> memory all the time by hitting the appropriate barrier implementation in 
> the host kernel. 
> 
> By improving the disk susbsystem we make this bug raise its ugly head
> with a vengeance - you can get a process in D (with an occasional child
> in Z state) simply by running an apt-get on 30-40 large packages. 
> 
> Is this correct place to have the sync - no idea. It may need to move
> to somewhere inside tlb.c. With the fence in exec.c it works (TM).
> 
> If I understand this correctly, this also needs to be an instruction 
> appropriate for the underlying host so just a barrier() will not cut 
> it. You have to fence. En-guarde... Touche... :)
> 
> Signed-off-by: Anton Ivanov <antivano@cisco.com>
> ---
>  arch/um/kernel/exec.c |    5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/arch/um/kernel/exec.c b/arch/um/kernel/exec.c
> index 0d7103c..7cb6805 100644
> --- a/arch/um/kernel/exec.c
> +++ b/arch/um/kernel/exec.c
> @@ -27,6 +27,11 @@ void flush_thread(void)
>  	ret = unmap(&current->mm->context.id, 0, STUB_START, 0, &data);
>  	ret = ret || unmap(&current->mm->context.id, STUB_END,
>  			   host_task_size - STUB_END, 1, &data);
> +#ifdef CONFIG_X86_32
> +	alternative("lock; addl $0,0(%%esp)", "mfence", X86_FEATURE_XMM2);
> +#else
> +	asm volatile("mfence":::"memory");
> +#endif

Why not mb()?
I'm not sure whether this fix is correct.

Thanks,
//richard

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel


  reply	other threads:[~2014-09-26 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 11:49 [uml-devel] [PATCH] Fix for "occasional userspace process in D/Z state" bug anton.ivanov
2014-09-26 11:56 ` Richard Weinberger [this message]
2014-09-26 12:35   ` Anton Ivanov (antivano)
2014-09-28  8:15   ` 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=5425547C.1080002@nod.at \
    --to=richard@nod.at \
    --cc=anton.ivanov@kot-begemot.co.uk \
    --cc=dwalter@google.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.