mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] avr32: deal with double restarts
Date: Thu, 13 Jan 2011 21:28:37 +0100	[thread overview]
Message-ID: <1294950517.26709.22.camel@hcegtvedt> (raw)
In-Reply-To: <E1PSom6-0008UE-DQ@ZenIV.linux.org.uk>

On Wed, 2010-12-15 at 10:39 +0000, Al Viro wrote:

Hi Al,

> a) take handling of reschedule, signals and keychains into a new helper -
> work_pending().  All looping is done there now; asm glue calls that if
> we have anything for it to do.
> 
> b) do_signal() gets explicit "may restart" flag as an argument; after
> the first call during that loop it gets unconditional 0.
> 
> c) sigreturn() sets a thread flag - TIF_NORESTART.  It is included into
> the "work_pending() has something to do" mask.  work_pending() clears
> it, clearing its may_restart flag if it had done so.

Testing this patch series on top of the latest kernel release it bombs
out quite early with a

Bus error at physical address 0x6c6110e4 (read access)
DTLB dump:
(...)

Do you have any additional information I might have overlooked? On what
hardware and how have you tested this?

<snipp patch>

> -asmlinkage void do_notify_resume(struct pt_regs *regs, struct thread_info *ti)
> +asmlinkage int work_pending(struct pt_regs *regs, struct thread_info *ti, int may_restart)

This line could be broken into two lines be within width limits, and in
addition the work_pending name conflicts with the work_pending macro in
workqueue.h.

<snipp>

-- 
Hans-Christian Egtvedt


      reply	other threads:[~2011-01-13 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 10:39 Al Viro
2011-01-13 20:28 ` Hans-Christian Egtvedt [this message]

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=1294950517.26709.22.camel@hcegtvedt \
    --to=hans-christian.egtvedt@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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

Powered by JetHome