All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Lang <Michael.Lang@jackal-net.at>
To: linux-kernel@vger.kernel.org
Subject: Kernel Panic when accessing NFS share and locking files
Date: Wed, 14 May 2008 19:27:36 +0200	[thread overview]
Message-ID: <482B2108.4090902@jackal-net.at> (raw)

Hi,

we encountered a serious problem, when using Solaris NFS (Server) 
accessing it with a CentOS5.1/RHEL5.1 client.
There are more occurrences of the problem, one i felt over when tried to 
recreate a different one was, that a unprivileged
User is able to Kernel Panic a machine with a few lines of code. I 
tested it with the result that 3 threads requesting a lock
on the same file already cause the kernel panic. Since this is my first 
kernel bug request, and it's at least for my understandig
a security problem, i will provide the code for recreation to a closed 
group only. Please point me to the right group ...

Call Trace:
  [<ffffffff80012323>] __fput+0x94/0x198
  [<ffffffff8002e2d2>] sys_fcntl+0x2d0/0x2dc
  [<ffffffff8005b28d>] tracesys+0xd5/0xe0
 Code: 0f 0b 68 8a de 28 80 c2 c7 07 48 89 c3 48 8b 03 48 85 c0 75
 RIP  [<ffffffff80027073>] locks_remove_flock+0xe4/0x122
 RSP <ffff81000be87e48>


regards
Michael Lang

             reply	other threads:[~2008-05-14 17:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 17:27 Michael Lang [this message]
2008-05-15  3:49 ` Kernel Panic when accessing NFS share and locking files Andrew Morton
2008-05-15  3:55   ` Arjan van de Ven
2008-05-15  7:20     ` Michael Lang
2008-05-15 11:30     ` Michael Lang
2008-05-19 21:13       ` J. Bruce Fields

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=482B2108.4090902@jackal-net.at \
    --to=michael.lang@jackal-net.at \
    --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 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.