public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: estellnb@gmail.com
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: block network access for certain users/groups
Date: Mon, 30 Aug 2010 20:55:43 +0900	[thread overview]
Message-ID: <201008302055.GEG52699.MJHtQLFOFOSFVO@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <AANLkTi=HpQNM_FeHDdejnh-q-RhLMFVK3-O5JgWKejA0@mail.gmail.com>

Elmar Stellnberger wrote:
> However if I compile the kernel module and try to load it that results
> in a kernel hang that I can only escape by Alt-PrnScr-S-U-B, no matter
> whether the module is loaded on boot time or in rl5. I have checked
> all required kernel options and built it like the following (using
> openSUSE 11.3):

This module is for 2.6.36 but openSUSE 11.3 uses 2.6.34 . Did you change
below spin_lock() to write_lock() and spin_unlock() to write_unlock()?

> > 	{
> > 		struct fs_struct *fs = current->fs;
> > 		struct vfsmount *mnt = current->nsproxy->pid_ns->proc_mnt;
> > 		struct path old_path;
> > 		struct path new_path = { mnt, mnt->mnt_root };
> > 		spin_lock(&fs->lock); /* was write_lock() till 2.6.35. */
> > 		old_path = fs->pwd;
> > 		fs->pwd = new_path;
> > 		spin_unlock(&fs->lock);
> > 		file = filp_open("kallsyms", O_RDONLY, 0);
> > 		spin_lock(&fs->lock);
> > 		fs->pwd = old_path;
> > 		spin_unlock(&fs->lock);
> > 	}

  reply	other threads:[~2010-08-30 11:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTin8w74SAe67ZPqPE0Q=0fPpZOHnTCnjAT+AduCY@mail.gmail.com>
2010-08-25 11:09 ` block network access for certain users/groups Elmar Stellnberger
2010-08-25 11:58   ` Tetsuo Handa
2010-08-26 12:28     ` Tetsuo Handa
2010-08-30 11:36       ` Elmar Stellnberger
2010-08-30 11:55         ` Tetsuo Handa [this message]
2010-08-25 16:02   ` Hagen Paul Pfeifer

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=201008302055.GEG52699.MJHtQLFOFOSFVO@I-love.SAKURA.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=estellnb@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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