All of lore.kernel.org
 help / color / mirror / Atom feed
From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: which context can't use queue_work() function?
Date: Sat, 3 Dec 2011 21:48:33 +0100	[thread overview]
Message-ID: <20111203204833.GA2228@grml> (raw)
In-Reply-To: <CAGoEaetQN0OpMuTdNGohutWydQfpE_e0bJ+=vX3iNSYbvi61xQ@mail.gmail.com>

Hi!

On 21:56 Sat 03 Dec     , onlyfever wrote:
> Hi,
>     I have a question about work queue.
> I use queue_work() function in my TTY driver's write function (ch_tty_write()).
> The TTY driver works fine,but when this driver is called from
> ppp_write() function system would crash.
> 
> static int ch_tty_write(struct tty_struct *tty,
> 					const unsigned char *buf, int count)
> {
>       ......
>       queue_work(xxx,xxxx);
>       return count;
> }
> 
> I want to know  which context can't use queue_work() function?
> Put the crash message below.
> 
> Unable to handle kernel NULL pointer dereference at virtual address 00000003

Please check that you have properly called "INIT_WORK" and do pass any null
pointers to either INIT_WORK or queue_work. If this does not help, please
give us a pointer on where to get your kernel tree.

	-Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com

  reply	other threads:[~2011-12-03 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03 13:56 which context can't use queue_work() function? onlyfever
2011-12-03 20:48 ` michi1 at michaelblizek.twilightparadox.com [this message]
2011-12-05 15:28   ` onlyfever

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=20111203204833.GA2228@grml \
    --to=michi1@michaelblizek.twilightparadox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.