All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: "Ph. Marek" <marek@bmlv.gv.at>
Cc: sct@redhat.com, adilger@turbolinux.com,
	linux-kernel@vger.kernel.org, ext3-users@redhat.com
Subject: Re: [PATCH] open files in kjounald (2)
Date: Sun, 21 Apr 2002 22:49:27 -0700	[thread overview]
Message-ID: <3CC3A467.AC73A469@zip.com.au> (raw)
In-Reply-To: <3.0.6.32.20020422072320.009347f0@pop3.bmlv.gv.at>

"Ph. Marek" wrote:
> 
> ...
> --- linux.ori/fs/jbd/journal.c  Mon Apr 22 06:28:54 2002
> +++ linux/fs/jbd/journal.c      Mon Apr 22 06:29:16 2002
> @@ -204,7 +204,6 @@
> 
>         lock_kernel();
>         daemonize();
> +       exit_files(current);
>         spin_lock_irq(&current->sigmask_lock);
>         sigfillset(&current->blocked);
>         recalc_sigpending(current);

Confused.  The daemonize() call makes kjournald use init's
files:

quad:/home/akpm# uname -a
Linux quad 2.4.19-pre7 #18 SMP Sun Apr 21 22:42:31 PDT 2002 i686 unknown
quad:/home/akpm# mount /dev/sdb6 /mnt/sdb6 -t ext3 < /etc/services
quad:/home/akpm# ps aux|tail -3
root       903  0.0  0.0     0    0 ?        SW   22:45   0:00 [kjournald]
root       904  0.0  0.0  2640  728 pts/0    R    22:45   0:00 ps aux
root       905  0.0  0.0  1680  528 pts/0    S    22:45   0:00 tail -3
quad:/home/akpm# ls -l /proc/903/fd
total 0
lrwx------    1 root     root           64 Apr 21 22:46 0 -> socket:[479]
lrwx------    1 root     root           64 Apr 21 22:46 10 -> /dev/initctl

That all looks good - every /proc/$(pidof kjournald)/fd
shows that the kjournald instances are using init's files.

Which kernel are you using?  Have you any theories as to why you're
seeing different behaviour?

-

  reply	other threads:[~2002-04-22  5:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22  5:23 [PATCH] open files in kjounald (2) Ph. Marek
2002-04-22  5:49 ` Andrew Morton [this message]
     [not found] <200204221056.04322.nahshon@actcom.co.il>
2002-04-22  8:25 ` Ph. Marek

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=3CC3A467.AC73A469@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=adilger@turbolinux.com \
    --cc=ext3-users@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek@bmlv.gv.at \
    --cc=sct@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 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.