From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Suspend2 merge: New exports.
Date: Fri, 17 Sep 2004 08:04:03 +1000 [thread overview]
Message-ID: <1095372242.5897.10.camel@laptop.cunninghams> (raw)
In-Reply-To: <20040916143322.GB32352@kroah.com>
Hi.
On Fri, 2004-09-17 at 00:33, Greg KH wrote:
> On Thu, Sep 16, 2004 at 09:20:19PM +1000, Nigel Cunningham wrote:
> >
> > This patch adds exports for functions used by suspend2. Needed, of
> > course, when suspend is compiled as modules.
>
> Why even allow suspend as a module? It seems like a pretty core chunk
> of code that should be present all the time.
It only needs to be loaded when you're suspending/resuming, so it's not
really core. Building it as modules also allows upgrading (at least
sometimes) without rebooting. Finally, my version of suspend is a lot
bigger than the implementation in the kernel at the moment because it
includes many more features.
[...]
> Why this change? buffer_busy() is not exported now.
You're right. It's a holdover from 2.4 that I missed cleaning.
> > -#ifdef CONFIG_COMPAT
> > EXPORT_SYMBOL(sys_ioctl);
> > -#endif
>
> What ioctls does suspend2 call? That seems very strange.
The console driver. People objected to direct usage of console functions
and suggested I use /dev/console for doing output. That's what I'm doing
now, although I do still have some direct usage to seek to get rid of.
(I'm not claiming my code is finished and perfect!)
> Why is the include needed here just to export a symbol (nevermind the
> fact that we should never export tainted in the first place.)
They're unrelated, actually. There used to be a couple of lines in here
that stopped us syncing if we oops part way through suspending. With
recent changes, it's no longer necessary. The fact that the include
isn't needed anymore wasn't noticed.
As to exporting tainted, I thought about this on the way to bed last
night, after another email. As I said previously, I was exporting it so
I could set a tainted flag when we've suspended, to save driver authors
headaches. It never occurred to me - as it has now - that this also
allows unscrupulous people to turn off flags. I don't think tainting is
necessary any more, so I'll happily drop this.
Regards,
Nigel
--
Nigel Cunningham
Pastoral Worker
Christian Reformed Church of Tuggeranong
PO Box 1004, Tuggeranong, ACT 2901
Many today claim to be tolerant. True tolerance, however, can cope with others
being intolerant.
next prev parent reply other threads:[~2004-09-16 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 11:20 Nigel Cunningham
2004-09-16 11:40 ` Arjan van de Ven
2004-09-16 11:54 ` Nigel Cunningham
2004-09-16 14:33 ` Greg KH
2004-09-16 22:04 ` Nigel Cunningham [this message]
2004-09-17 7:28 ` Christoph Hellwig
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=1095372242.5897.10.camel@laptop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=akpm@digeo.com \
--cc=greg@kroah.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®