From: Pavel Machek <pavel@ucw.cz>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH -mm] freeze/thaw fs when BLOCK=n
Date: Fri, 17 Nov 2006 16:18:21 +0100 [thread overview]
Message-ID: <20061117151820.GA8867@elf.ucw.cz> (raw)
In-Reply-To: <20061116213600.9983f4f9.randy.dunlap@oracle.com>
Hi!
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix freeze/thaw filesystems with CONFIG_BLOCK disabled:
> kernel/power/process.c:124: warning: implicit declaration of function 'freeze_fil
> esystems'
> kernel/power/process.c:189: warning: implicit declaration of function 'thaw_files
> ystems'
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
I believe we'll simply want to remove {thaw,freeze}_filesystems. XFS
problem is solved with freezeable workqueues, and
{thaw,freeze}_filesystems has problems if someone is creating dm
snapshots in the meantime.
Pavel
> ---
> include/linux/buffer_head.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> --- linux-2619-rc5mm2.orig/include/linux/buffer_head.h
> +++ linux-2619-rc5mm2/include/linux/buffer_head.h
> @@ -314,7 +314,8 @@ static inline void invalidate_inode_buff
> static inline int remove_inode_buffers(struct inode *inode) { return 1; }
> static inline int sync_mapping_buffers(struct address_space *mapping) { return 0; }
> static inline void invalidate_bdev(struct block_device *bdev, int destroy_dirty_buffers) {}
> -
> +static inline void freeze_filesystems(void) {}
> +static inline void thaw_filesystems(void) {}
>
> #endif /* CONFIG_BLOCK */
> #endif /* _LINUX_BUFFER_HEAD_H */
>
>
> ---
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2006-11-17 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 5:36 Randy Dunlap
2006-11-17 15:18 ` Pavel Machek [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=20061117151820.GA8867@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rjw@sisk.pl \
/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®