From: "Felipe Dias" <felipediassss@gmail.com>
To: "Jiri Slaby" <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: textsearch in module = BUG: scheduling while atomic
Date: Sun, 4 Nov 2007 19:57:08 -0300 [thread overview]
Message-ID: <3c16e8dc0711041457r684fb42fpc3845a941162b65d@mail.gmail.com> (raw)
In-Reply-To: <472E458B.50903@gmail.com>
I change the algo, from "bm" to "kmp" and probably resolve. I will
make more tests and if error occour i post latter...
Thanks so much.
Felipe Dias
On 11/4/07, Jiri Slaby <jirislaby@gmail.com> wrote:
> On 11/04/2007 11:16 PM, Jiri Slaby wrote:
> > On 11/04/2007 11:05 PM, Felipe Dias wrote:
> >> Ow sorry... the warning:
> >>
> >> BUG: scheduling while atomic: gnome-cups-icon/0x00000101/3827
> >> [<c02aefe6>] __sched_text_start+0x56/0x7c8
> >> [<c0130139>] autoremove_wake_function+0x14/0x33
> >> [<c0119284>] __wake_up_common+0x35/0x53
> >> [<c01197f6>] __wake_up+0x32/0x43
> >> [<c02af847>] wait_for_completion+0x6a/0x9f
> >> [<c011b6ae>] default_wake_function+0x0/0xc
> >> [<c012cdff>] call_usermodehelper_keys+0xad/0xc5
> >> [<c012ceec>] request_module+0xd5/0xe6
> >
> > Seems like it is not inteded for using in atomic at all (you probably passed an
> > unknown algo here to the prepare function). You seem to have to use a workqueue
> > if it is possible or prepare the serach before the interrupt occurs.
>
> Or pass 0 instead of TS_AUTOLOAD.
>
next prev parent reply other threads:[~2007-11-04 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 17:15 Felipe Dias
2007-11-04 17:57 ` Jiri Slaby
[not found] ` <3c16e8dc0711041222w6bc67b3fn8320e982ffd723b0@mail.gmail.com>
[not found] ` <472E346E.90309@gmail.com>
2007-11-04 22:05 ` Felipe Dias
2007-11-04 22:16 ` Jiri Slaby
2007-11-04 22:19 ` Jiri Slaby
2007-11-04 22:57 ` Felipe Dias [this message]
2007-11-05 14:02 ` Jiri Slaby
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=3c16e8dc0711041457r684fb42fpc3845a941162b65d@mail.gmail.com \
--to=felipediassss@gmail.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®