From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Lang <Michael.Lang@jackal-net.at>
Cc: linux-kernel@vger.kernel.org,
"J. Bruce Fields" <bfields@fieldses.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Kernel Panic when accessing NFS share and locking files
Date: Wed, 14 May 2008 20:49:32 -0700 [thread overview]
Message-ID: <20080514204932.13243cab.akpm@linux-foundation.org> (raw)
In-Reply-To: <482B2108.4090902@jackal-net.at>
On Wed, 14 May 2008 19:27:36 +0200 Michael Lang <Michael.Lang@jackal-net.at> wrote:
> 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>
Which kernel version is being used?
next prev parent reply other threads:[~2008-05-15 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 17:27 Kernel Panic when accessing NFS share and locking files Michael Lang
2008-05-15 3:49 ` Andrew Morton [this message]
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=20080514204932.13243cab.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Michael.Lang@jackal-net.at \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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