From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Pete Zaitcev" <zaitcev@redhat.com>
Cc: "Ingo Molnar" <mingo@elte.hu>, "Frans Pop" <elendil@planet.nl>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
gregkh@suse.de, "Christoph Lameter" <clameter@sgi.com>
Subject: Re: [sched-devel/latest] WARNING: at mm/slub.c:2443
Date: Wed, 23 Apr 2008 20:35:15 +0300 [thread overview]
Message-ID: <84144f020804231035w3fdb10aax4b90dc4e0bc1957d@mail.gmail.com> (raw)
In-Reply-To: <20080423101123.a69e4945.zaitcev@redhat.com>
On Wed, Apr 23, 2008 at 8:11 PM, Pete Zaitcev <zaitcev@redhat.com> wrote:
> > --- a/drivers/usb/mon/mon_text.c
> > +++ b/drivers/usb/mon/mon_text.c
> > @@ -449,6 +449,7 @@ static struct mon_event_text *mon_text_read_wait(struct mon_reader_text *rp,
> > if (file->f_flags & O_NONBLOCK) {
> > set_current_state(TASK_RUNNING);
> > remove_wait_queue(&rp->wait, &waita);
> > + kmem_cache_free(rp->e_slab, ep);
> > return ERR_PTR(-EWOULDBLOCK);
>
> The code looks like this:
>
> while ((ep = mon_text_fetch(rp, mbus)) == NULL) {
>
> if (file->f_flags & O_NONBLOCK) {
> set_current_state(TASK_RUNNING);
> remove_wait_queue(&rp->wait, &waita);
> return ERR_PTR(-EWOULDBLOCK);
>
> It's impossible to get inside the while() with non-null ep,
> so your patch doesn't fix anything (even if kmem_cache_free
> can survive a NULL object).
Yeah, I need a new pair of glasses. Thanks.
On Wed, Apr 23, 2008 at 8:11 PM, Pete Zaitcev <zaitcev@redhat.com> wrote:
> Any other ideas?
Well, a race in mon_text_release() after the kmem_cache_free() loop
and the call to kmem_cache_destroy() but looks like that can't happen
either. Frans, is this easily triggerable? If so, can you try with
CONFIG_SLAB and CONFIG_DEBUG_SLAB enabled instead?
next prev parent reply other threads:[~2008-04-23 17:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 21:10 Frans Pop
2008-04-22 13:40 ` Ingo Molnar
2008-04-22 17:27 ` Pekka J Enberg
2008-04-22 19:22 ` Christoph Lameter
2008-04-22 21:32 ` Pete Zaitcev
2008-04-23 5:21 ` Pekka J Enberg
2008-04-23 6:51 ` Pete Zaitcev
2008-04-23 7:31 ` Pekka Enberg
2008-04-23 7:34 ` Pekka Enberg
2008-04-23 17:13 ` Pete Zaitcev
2008-04-23 7:38 ` Pekka J Enberg
2008-04-23 17:11 ` Pete Zaitcev
2008-04-23 17:35 ` Pekka Enberg [this message]
2008-04-23 18:15 ` Frans Pop
2008-04-24 14:13 ` Frans Pop
2008-05-02 9:17 ` Pekka Enberg
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=84144f020804231035w3fdb10aax4b90dc4e0bc1957d@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=clameter@sgi.com \
--cc=elendil@planet.nl \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zaitcev@redhat.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
all inboxes | Powered by JetHome®