From: Martin Schlemmer <azarah@gentoo.org>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Sensors <sensors@stimpy.netroedge.com>, Greg KH <greg@kroah.com>
Subject: Re: [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d during rmmod (2.5.70-bk1[1234]))
Date: 13 Jun 2003 08:08:48 +0200 [thread overview]
Message-ID: <1055484528.5281.4544.camel@workshop.saharacpt.lan> (raw)
In-Reply-To: <20030613023651.GA1401@earth.solarsys.private>
On Fri, 2003-06-13 at 04:36, Mark M. Hoffman wrote:
> > Nope, this do not fix it.
> >
> > The problem is actually at the i2c driver side. From
> > drivers/i2c/i2c-core.c in i2c_del_driver(), we have:
> <cut>
>
> To recap: list_for_each_safe() is not safe for deleting other than
> the current "item". But I disagree with you Martin because I think
> the usage in i2c_del_driver is ok as is; and that w83781d.c should
> change...
>
Right, I will not argue, as I was not sure on usage (and thus the
mail). Might be right thing (tm) to send a patch to make it more
clear that its only 'safe' for current item deletion (against
list.h) ?
> My first patch was naive; the patch below solves the problem by
> letting w83781d_detach_client remove the three clients (1 * primary
> + 2 * subclients) independently. It's a noisy patch because I had
> to change the way the subclients were kmalloc'ed - sorry. The meat
> is around line 1422. This patch works for me... comments?
>
I did try this way, but did it rather brutish =) It thus still did
not fix it. Your patch looks good ... I will try it tonight at home.
Regards,
--
Martin Schlemmer
next prev parent reply other threads:[~2003-06-13 5:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 18:37 [OOPS] w83781d during rmmod (2.5.69-bk17) Mark M. Hoffman
[not found] ` <3ED8067E.1050503@paradyne.com>
2003-06-01 14:38 ` [RFC PATCH] " Mark M. Hoffman
2003-06-02 17:20 ` Greg KH
2003-06-03 5:22 ` Martin Schlemmer
2003-06-03 19:43 ` Philip Pokorny
2003-06-04 5:57 ` Martin Schlemmer
2003-06-05 2:39 ` Mark M. Hoffman
2003-06-05 19:47 ` Greg KH
2003-06-09 5:34 ` Martin Schlemmer
2003-06-10 5:38 ` Martin Schlemmer
2003-06-10 5:41 ` OOPS w83781d during rmmod (2.5.70-bk1[1234]) Mark M. Hoffman
2003-06-10 5:51 ` Martin Schlemmer
2003-06-11 5:44 ` Martin Schlemmer
2003-06-12 6:57 ` [RFC][2.5] list_for_each_safe not so safe (was Re: OOPS w83781d during rmmod (2.5.70-bk1[1234])) Martin Schlemmer
2003-06-13 2:36 ` Mark M. Hoffman
2003-06-13 6:08 ` Martin Schlemmer [this message]
2003-06-14 6:26 ` Martin Schlemmer
2003-06-16 18:41 ` Greg KH
2003-09-03 20:54 ` [PATCH 2.6] Fix conversion from milli volts in store_in_reg() for w83781d.c Martin Schlemmer
2003-09-04 18:40 ` Greg KH
2003-09-07 15:41 ` Andrey Borzenkov
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=1055484528.5281.4544.camel@workshop.saharacpt.lan \
--to=azarah@gentoo.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhoffman@lightlink.com \
--cc=sensors@stimpy.netroedge.com \
/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
Powered by JetHome