linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@digeo.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: Shared memory shmat/dt not working well in
Date: Tue, 1 Oct 2002 18:02:27 +0200	[thread overview]
Message-ID: <35FD2132190@vcnet.vc.cvut.cz> (raw)

On  1 Oct 02 at 14:09, Hugh Dickins wrote:
> Exemplary bug report!  Many thanks for taking so much trouble to
> reproduce the problem.  Patch below (against 2.5.39) should fix it:
> I'll send Linus and Andrew when I can get hold of a 2.5.40 tree.

You are my hero! It fixed dnetc client failing with SIGSEGV after call
to sys_mprotect(). 

Unfortunately it did not fixed another problem I have with sys_mprotect.
If I start X, system stops to do anything useful. After SAK I could
do remote connect and running 'w' and 'ps axf' moved them to 'D' state.
Clean sysrq-u,s,b was possible. 2.5.40 kernel plus Hugh's patch, 100%
reproducible with 2.5.40 SMP (non-preempt) kernel running on UP here...
                                    Thanks,
                                                Petr Vandrovec
                                                

Oct  1 17:47:35 vana kernel: SysRq : SAK
Oct  1 17:47:35 vana kernel: SAK: killed process 1482 (XFree86): fd#3 opened to the tty
...
Oct  1 17:47:55 vana kernel: XFree86       D DADE7A60     0  1482   1481                     (NOTLB)
Oct  1 17:47:55 vana kernel: Call Trace:
Oct  1 17:47:55 vana kernel:  [<c01167df>]schedule+0x3bb/0x488
Oct  1 17:47:55 vana kernel:  [<c019bdd5>]rwsem_down_read_failed+0x165/0x188
Oct  1 17:47:55 vana kernel:  [<c0114adb>].text.lock.fault+0x7/0x6c
Oct  1 17:47:55 vana kernel:  [<c01146b0>]do_page_fault+0x0/0x424
Oct  1 17:47:55 vana kernel:  [<c01323a2>]do_generic_file_read+0xee/0x35c
Oct  1 17:47:55 vana kernel:  [<c0132602>]do_generic_file_read+0x34e/0x35c
Oct  1 17:47:55 vana kernel:  [<c01328cb>]__generic_file_aio_read+0x187/0x1a0
Oct  1 17:47:55 vana kernel:  [<c0132610>]file_read_actor+0x0/0x134
Oct  1 17:47:55 vana kernel:  [<c01372bc>]free_block+0x168/0x250
Oct  1 17:47:55 vana kernel:  [<c0107ec9>]error_code+0x2d/0x38
Oct  1 17:47:55 vana kernel:  [<c011216f>]flush_tlb_mm+0x1b/0x70
Oct  1 17:47:55 vana kernel:  [<c0133ed1>]change_protection+0x1a1/0x1dc
Oct  1 17:47:55 vana kernel:  [<c01341ed>]mprotect_fixup+0x16d/0x188
Oct  1 17:47:55 vana kernel:  [<c0134392>]sys_mprotect+0x18a/0x2c4
Oct  1 17:47:55 vana kernel:  [<c0107467>]syscall_call+0x7/0xb
...
Oct  1 17:47:55 vana kernel: w             D DADE7A60     0  1563   1558                     (NOTLB)
Oct  1 17:47:55 vana kernel: Call Trace:
Oct  1 17:47:55 vana kernel:  [<c015be79>]dput+0x19/0x1d4
Oct  1 17:47:55 vana kernel:  [<c019bdd5>]rwsem_down_read_failed+0x165/0x188
Oct  1 17:47:55 vana kernel:  [<c016fecf>].text.lock.array+0x6d/0x10e
Oct  1 17:47:55 vana kernel:  [<c013b238>]__get_free_pages+0x28/0x60
Oct  1 17:47:55 vana kernel:  [<c016c807>]proc_info_read+0x4f/0x108
Oct  1 17:47:55 vana kernel:  [<c0146580>]vfs_read+0xb4/0x134
Oct  1 17:47:55 vana kernel:  [<c014676a>]sys_read+0x2a/0x3c
Oct  1 17:47:55 vana kernel:  [<c0107467>]syscall_call+0x7/0xb
...
Oct  1 17:47:55 vana kernel: ps            D DADE7A60     0  1583   1582                     (NOTLB)
Oct  1 17:47:55 vana kernel: Call Trace:
Oct  1 17:47:55 vana kernel:  [<c015be79>]dput+0x19/0x1d4
Oct  1 17:47:55 vana kernel:  [<c019bdd5>]rwsem_down_read_failed+0x165/0x188
Oct  1 17:47:55 vana kernel:  [<c016fecf>].text.lock.array+0x6d/0x10e
Oct  1 17:47:55 vana kernel:  [<c013b238>]__get_free_pages+0x28/0x60
Oct  1 17:47:55 vana kernel:  [<c016c807>]proc_info_read+0x4f/0x108
Oct  1 17:47:55 vana kernel:  [<c0146580>]vfs_read+0xb4/0x134
Oct  1 17:47:55 vana kernel:  [<c014676a>]sys_read+0x2a/0x3c
Oct  1 17:47:55 vana kernel:  [<c0107467>]syscall_call+0x7/0xb

             reply	other threads:[~2002-10-01 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 16:02 Petr Vandrovec [this message]
2002-10-01 17:14 ` [PATCH] Re: Shared memory shmat/dt not working well in Hugh Dickins
2002-10-01 17:56   ` Petr Vandrovec
2002-10-01 19:01   ` Christoph Hellwig
2002-10-01 19:15   ` Andrew Morton

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=35FD2132190@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=akpm@digeo.com \
    --cc=hugh@veritas.com \
    --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;
as well as URLs for NNTP newsgroup(s).