kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: suspicious RCU usage?
Date: Tue, 6 Mar 2012 22:30:29 +0700	[thread overview]
Message-ID: <CAGdaadaRo1OWU=POJhH6KOsPOigmogBSa53mCtgiHXoQybntyQ@mail.gmail.com> (raw)
In-Reply-To: <CA+MoWDq2tuZcwNxAuUi7EzxyiOu1noPJAKqxywiJtvUgzk+99A@mail.gmail.com>

Hi.... :)

On Sun, Mar 4, 2012 at 20:16, Peter Senna Tschudin
<peter.senna@gmail.com> wrote:
> [ ?858.634435] kernel/pid.c:425 find_task_by_pid_ns() needs
> rcu_read_lock() protection!

hmm....ok....kernel said that.... so...

> int yfkm2_is_pid_running(pid_t pid)
> {
> ? ? ? ?struct task_struct *q;
>
> ? ? ? ?q = find_task_by_vpid(pid);

I think this section that makes kernel barf. It wants you to grab
rcu_read_lock(), right before you do find_task_by_vpid().

What do you think? :)

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

      reply	other threads:[~2012-03-06 15:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 13:16 suspicious RCU usage? Peter Senna Tschudin
2012-03-06 15:30 ` Mulyadi Santosa [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='CAGdaadaRo1OWU=POJhH6KOsPOigmogBSa53mCtgiHXoQybntyQ@mail.gmail.com' \
    --to=mulyadi.santosa@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).