public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Don't call sysfs_del_hardif() in atomic context
Date: Sun, 31 Oct 2010 17:04:48 +0100	[thread overview]
Message-ID: <201010311704.48893.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <1288539158-26976-1-git-send-email-linus.luessing@web.de>

[-- Attachment #1: Type: Text/Plain, Size: 1068 bytes --]

Linus Lüssing wrote:
> sysfs_del_hardif invokes kobject_put, which might sleep. However, we
> are not allowed to sleep during a call_rcu. There is also no need to
> do the removal with an atomic call_rcu, as kobject_put only frees the
> kobject when there is no more reference to it anyway.
> 
> This commit basically revokes 7f32f2e8d97150ba5b80410dda86b01b0879fe8d,
> despite not reintroducing the synchronize_rcu, our rcu_barrier should
> handle this.

This is an extreme bad idea as we would free the object before the rcu grace 
period is over. This would mean that any parallel run through the list would 
probably access memory which is invalid. So this is a good way to crash your 
machine.

What makes you think that kobject_put sleeps? There is no code which proves 
it. The only reason would be that kobject_put -> kobject_release -> 
kobject_cleanup -> ... sleeps. Please complete that chain to show were the 
problem is. If it really sleeps then please only do the kobject related 
cleanup outside of call_rcu.

Best regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-10-31 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 15:32 [B.A.T.M.A.N.] [PATCH] batman-adv: Don't call sysfs_del_hardif() in atomic context Linus Lüssing
2010-10-31 16:04 ` Sven Eckelmann [this message]
2010-10-31 16:12   ` Sven Eckelmann
2010-10-31 21:07     ` [B.A.T.M.A.N.] [PATCHv2] " Linus Lüssing
2010-11-04 13:31       ` Marek Lindner

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=201010311704.48893.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.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