From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] Per kthread freezer flags
Date: Fri, 30 Jul 2004 08:46:31 +1000 [thread overview]
Message-ID: <1091141191.2703.42.camel@desktop.cunninghams> (raw)
In-Reply-To: <20040729224422.GG18623@elf.ucw.cz>
Hi.
On Fri, 2004-07-30 at 08:44, Pavel Machek wrote:
> Hi!
>
> > > > - pd->cdrw.thread = kthread_run(kcdrwd, pd, "%s", pd->name);
> > > > + pd->cdrw.thread = kthread_run(kcdrwd, pd, "%s", 0, pd->name);
> > > > if (IS_ERR(pd->cdrw.thread)) {
> > > > printk("pktcdvd: can't start kernel thread\n");
> > > > ret = -ENOMEM;
> > >
> > > What if someone does swapon /dev/pktdvd0?
> >
> > Sorry. That's my ignorance. I thought the packet writer was only for
> > writing :>
>
> Well, swapon /dev/pktdvd would be *very* bad idea as optical drives
> are very slow, but PF_NOFREEZE is more correct here.
Okay. I'll do a new patch for Andrew for this and the following
corrections.
[...]
> > >
> > > I guess softinterrupts may be neccessary for suspend... Random drivers may use
> > > them, right?
> >
> > I made this change at least a month ago and no one using suspend2 has
> > had any problems since, so perhaps not. Then again, with the voluntary
> > preemption (from what I've seen of comments about it) this would be a
> > definite yes.
>
> Ok.
Just in case I wasn't clear, by 'a definite yes', I mean you're
absolutely right - it should be NOFREEZE.
Regards,
Nigel
next prev parent reply other threads:[~2004-07-29 22:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 7:22 [Patch] Per kthread freezer flags Nigel Cunningham
2004-07-28 21:20 ` Andrew Morton
2004-07-28 22:25 ` Nigel Cunningham
2004-07-28 22:30 ` Felipe Alfaro Solana
2004-07-28 22:27 ` Nigel Cunningham
2004-07-28 22:36 ` Nigel Cunningham
2004-07-28 23:21 ` Felipe Alfaro Solana
2004-07-29 0:46 ` Nigel Cunningham
2004-07-29 10:02 ` Felipe Alfaro Solana
2004-07-29 12:11 ` Nigel Cunningham
2004-07-29 16:10 ` Felipe Alfaro Solana
2004-07-29 22:39 ` Nigel Cunningham
2004-07-30 8:12 ` Felipe Alfaro Solana
2004-07-29 22:57 ` Felipe Alfaro Solana
2004-07-29 23:01 ` Nigel Cunningham
2004-07-29 19:04 ` Pavel Machek
2004-07-29 22:24 ` Nigel Cunningham
2004-07-29 22:44 ` Pavel Machek
2004-07-29 22:46 ` Nigel Cunningham [this message]
2004-07-29 23:25 ` [Patch] Per kthread freezer flags (Version 2) Nigel Cunningham
2004-07-30 9:18 ` Pavel Machek
2004-07-31 16:53 ` Felipe Alfaro Solana
2004-07-30 12:11 ` [Patch] Per kthread freezer flags Peter Osterlund
2004-07-30 22:15 ` Nigel Cunningham
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=1091141191.2703.42.camel@desktop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.