public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "André Pereira de Almeida" <andre@cachola.com.br>
To: Valdis.Kletnieks@vt.edu
Cc: Chris Wedgwood <cw@f00f.org>, linux-kernel@vger.kernel.org
Subject: Re: A patch for the file kernel/fork.c
Date: Wed, 04 May 2005 16:35:33 -0300	[thread overview]
Message-ID: <42792405.4020309@cachola.com.br> (raw)
In-Reply-To: <200505041911.j44JBhda022528@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:

>On Wed, 04 May 2005 15:26:44 -0300, =?ISO-8859-1?Q?Andr=E9_Pereira_de_Almeida?= said:
>
>  
>
>>In a preemptible kernel with the serport module and a serial port try to 
>>run the following program:
>>    
>>
>
>  
>
>>and kill it.
>>In my case it will hang the computer. I think this is a problem with the 
>>serport module. With this patch, the serial mouse stop working, but the 
>>computer don't hang.
>>    
>>
>
>The fact that the mouse stops working is indicative that this patch doesn't
>actually fix the problem, it's just pushing it around in the kernel - sooner
>or later something *else* is going to go pear-shaped on the null *mm.  The right
>fix is to figure out why mm is bogus and fix that issue.
>  
>
This patch is not to fix this problem, but to minimize a bug in other 
modules (in this case I think it's in the serport module) and to keep 
the system working, at least to make a clean shutdown or terminate some 
important process cleanly.

This patch is in the mm_release that should return a null *mm anyway.

The bogus mm came from a pagefault in the do_exit function in 
kernel/exit.c that occured after the exit_mm call. This pagefault, in my 
case, come from a filp_close call that called tty_wakeup. I'm trying to 
identify this problem, but a pagefault like this may came from several 
different modules.
André

      parent reply	other threads:[~2005-05-04 19:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 14:46 A patch for the file kernel/fork.c André Pereira de Almeida
2005-05-04 17:54 ` Chris Wedgwood
2005-05-04 18:26   ` André Pereira de Almeida
2005-05-04 18:43     ` Chris Wedgwood
2005-05-04 19:04       ` André Pereira de Almeida
2005-05-04 19:16         ` Alexander Nyberg
2005-05-04 19:41           ` Andrew Morton
2005-05-04 20:54             ` André Pereira de Almeida
2005-05-04 21:21             ` Alexander Nyberg
2005-05-05 13:48               ` Steven Rostedt
2005-05-05 15:32                 ` Alexander Nyberg
2005-05-07  1:08                   ` Andrew Morton
2005-05-04 19:11     ` Valdis.Kletnieks
2005-05-04 19:34       ` Dmitry Torokhov
2005-05-04 19:35       ` André Pereira de Almeida [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=42792405.4020309@cachola.com.br \
    --to=andre@cachola.com.br \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    /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