search for: journal_init

This patch contains the following cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL: - journal.c: journal_recover Signed-off-by: Adrian Bunk <bunk at stusta.de> --- fs/jbd/journal.c | 34 ++++++++++++++-------------------- fs/jbd/revoke.c...

This patch contains the following possible cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features - journal.c: journal_recover Please check which of these changes do make sense. Signed-off-by: Adrian Bunk <bunk a...

...es changed, 16 insertions(+), 19 deletions(-) --- linux-2.6.12-rc2-mm3-full/include/linux/jbd.h.old 2005-04-21 03:39:15.000000000 +0200 +++ linux-2.6.12-rc2-mm3-full/include/linux/jbd.h 2005-04-21 03:43:21.000000000 +0200 @@ -900,8 +900,6 @@ int start, int len, int bsize); extern journal_t * journal_init_inode (struct inode *); extern int journal_update_format (journal_t *); -extern int journal_check_used_features - (journal_t *, unsigned long, unsigned long, unsigned long); extern int journal_check_available_features (journal_t *, unsigned long, unsigned long, unsigned long)...

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

...-ioctl (2009-04-01) initialised: dm-devel at redhat.com [ 51.178486] initcall dm_init+0x0/0x34 [dm_mod] returned 0 after 12924 usecs [ 51.200983] calling init_mbcache+0x0/0xd [mbcache] @ 432 [ 51.206290] initcall init_mbcache+0x0/0xd [mbcache] returned 0 after 0 usecs [ 51.215744] calling journal_init+0x0/0x7f [jbd] @ 432 [ 51.221142] initcall journal_init+0x0/0x7f [jbd] returned 0 after 339 usecs [ 51.232370] calling init_ext3_fs+0x0/0x5e [ext3] @ 432 [ 51.237806] initcall init_ext3_fs+0x0/0x5e [ext3] returned 0 after 292 usecs [ 51.254648] kjournald starting. Commit interval 5 second...

Lots of changes since v2, too much to remember or summarize. Please ignore patch 11/11, it's just for my testing. Rich.