All of lore.kernel.org
 help / color / mirror / Atom feed
From: dave young <Young@farstone.com>
To: linux-kernel@vger.kernel.org
Subject: loop's kernel_thread
Date: Mon, 24 Mar 2003 09:35:22 +0800	[thread overview]
Message-ID: <3E7E60DA.6030000@farstone.com> (raw)
In-Reply-To: 3E7E0B37.5060505@portrix.net

hi all
    I'm being  modified loop block device driver for multi files binded 
to one loop device,
but the loop_thread sometimes seems locking the kernel.

static int loop_thread(void *data)
{
        struct loop_device *lo = data;
        struct buffer_head *bh;

        daemonize();
        exit_files(current);

        printk(KERN_INFO "i am here\n");
        sprintf(current->comm, "loop%i", lo->lo_number);

        spin_lock_irq(&current->sigmask_lock);
        sigfillset(&current->blocked);
        flush_signals(current);
        spin_unlock_irq(&current->sigmask_lock);

        current->policy = SCHED_OTHER;
        current->nice = -20;
.....
}
        It seems that  process name is still "mount" .It should be 
"loop0,loop1,etc.", isn't it?

        Anyone can help me?


      parent reply	other threads:[~2003-03-24  1:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-23 19:29 i2c-via686a driver Jan Dittmer
2003-03-23 20:27 ` Christoph Hellwig
2003-03-23 20:36   ` Dominik Kubla
2003-03-23 20:48     ` Christoph Hellwig
2003-03-23 21:33       ` Jan Dittmer
2003-03-23 21:41         ` Christoph Hellwig
2003-03-23 21:38       ` Jan Dittmer
2003-03-25  3:53         ` Greg KH
2003-03-25  3:54         ` Greg KH
2003-03-25  9:12           ` Jan Dittmer
2003-03-25 17:10             ` Greg KH
2003-03-24  1:35 ` dave young [this message]

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=3E7E60DA.6030000@farstone.com \
    --to=young@farstone.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 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.