search for: journal_info

Hello, Stephen, It seem that in the presence of several jornalling file systems in the kernel some mechanism is needed for proper sharing of the ->journal_info pointer in the task_struct. One journalled file system can indirectly call another during page fault in copy_from_user, quota file modification, or __alloc_pages()->balance_classzone()->shrink_cache()->vm_writeback() sequence. (Actually, I don't understand when prevents ext3 from re...

Hi I am hitting this Warning reproducible, the workload is a ceph osd, kernel ist 3.1.0-rc5. Best Regards, martin [ 5472.099766] ------------[ cut here ]------------ [ 5472.099833] WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]() [ 5472.099838] Hardware name: MS-96B3 [ 5472.099842] Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit psmouse sp5100_tco

...; record_root_in_trans(h, root); + + return ret; +} + +static struct btrfs_trans_handle *start_transaction(struct btrfs_root *root, + int num_items, int wait) +{ + struct btrfs_transaction *cur_trans; + struct btrfs_trans_handle *h; + u64 num_bytes = 0; + bool nested_trans = (current->journal_info); + bool committed = false; + int ret; + + num_bytes = calculate_bytes_needed(root, num_items); + +again: + h = kmem_cache_alloc(btrfs_trans_handle_cachep, GFP_NOFS); + if (!h) + return ERR_PTR(-ENOMEM); + + mutex_lock(&root->fs_info->trans_mutex); + if (!root->fs_info->log_root_re...

...2 self_exec_id; /* Protection of (de-)allocation: mm, files, fs, tty */ spinlock_t alloc_lock; }; /* --- 399,407 ---- u32 self_exec_id; /* Protection of (de-)allocation: mm, files, fs, tty */ spinlock_t alloc_lock; + + /* journalling filesystem info */ + void *journal_info; }; /* *************** *** 485,491 **** sig: &init_signals, \ pending: { NULL, &tsk.pending.head, {{0}}}, \ blocked: {{0}}, \ - alloc_lock:...

...**** u32 self_exec_id; /* Protection of (de-)allocation: mm, files, fs, tty */ spinlock_t alloc_lock; }; /* --- 399,407 ---- u32 self_exec_id; /* Protection of (de-)allocation: mm, files, fs, tty */ spinlock_t alloc_lock; + + /* journalling filesystem info */ + void *journal_info; }; /*

Hi all !!! I have got a MOSIX-Cluster and wanted to upgrade to ext3-fs, but that didn't work out. The ext3-fs patch FAILED to patch the MOSIX-kernel and if I tried to apply the ext3- patch before, the MOSIX-patch failed. Can someone help me with that ? Perhaps someone knows of a conclusion for that problem or can tell me where to get a MOSIX-patch for 2.4.15. I would be glad to hear from

The freeze rwsem is taken by sb_start_intwrite() and dropped during the commit_ or end_transaction(). In the async case, that happens in a worker thread. Tell lockdep the calling thread is releasing ownership of the rwsem and the async thread is picking it up. Josef and I worked out a more complicated solution that made the async commit thread join and potentially get a later transaction, but

jbd2_journal_restart() would restart a handle. In this function, it calls start_this_handle(). Before calling start_this_handle()?subtract 1 from transaction->t_updates. If start_this_handle() succeeds, transaction->t_updates increases by 1 in it. But if start_this_handle() fails, transaction->t_updates does not increase. So, when commit the handle's transaction in

...e included in the wiki change log link above. Here are some items that may interest you in this release: * Fix MDS crash when using open-unlinked directories. This problem was a regression introduced in 1.8.2. https://bugzilla.lustre.org/show_bug.cgi?id=22177 * The lustre client uses current->journal_info to pass locking information down to lower layers. This can trigger a kernel oops under memory pressure. https://bugzilla.lustre.org/show_bug.cgi?id=22035 * Some "lfs" commands can now be run as a non-privileged user again. https://bugzilla.lustre.org/show_bug.cgi?id=22127 * The 1.8.2 cl...

...e included in the wiki change log link above. Here are some items that may interest you in this release: * Fix MDS crash when using open-unlinked directories. This problem was a regression introduced in 1.8.2. https://bugzilla.lustre.org/show_bug.cgi?id=22177 * The lustre client uses current->journal_info to pass locking information down to lower layers. This can trigger a kernel oops under memory pressure. https://bugzilla.lustre.org/show_bug.cgi?id=22035 * Some "lfs" commands can now be run as a non-privileged user again. https://bugzilla.lustre.org/show_bug.cgi?id=22127 * The 1.8.2 cl...

I am running Debian Potato with kernel 2.4.27-rc3 on a Sparc Server 20, 128MB RAM machine. After few hours I get the following error in the syslog kernel file Jul 15 01:09:25 mudshark kernel: Assertion failure in journal_stop() at transaction.c:1418: "journal_current_handle() == handle" Jul 15 01:09:25 mudshark kernel: kernel BUG at transaction.c:1418! Jul 15 01:09:25 mudshark kernel:

.../linux/jbd.h:241: for each function it appears in.) /src/linux-2.4.13/include/linux/jbd.h:242: warning: control reaches end of non-void function /src/linux-2.4.13/include/linux/jbd.h: In function `journal_current_handle': /src/linux-2.4.13/include/linux/jbd.h:624: structure has no member named `journal_info' /src/linux-2.4.13/include/linux/jbd.h:625: warning: control reaches end of non-void function make[2]: *** [sysctl.o] Error 1 make[2]: Leaving directory `/src/linux-2.4.13/kernel' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory `/src/linux-2.4.13/kernel' make: *** [_dir_ker...

...c b/fs/btrfs/transaction.c index 04bbfb1..6d0d5a0 100644 --- a/fs/btrfs/transaction.c +++ b/fs/btrfs/transaction.c @@ -312,6 +312,7 @@ static struct btrfs_trans_handle *start_transaction(struct btrfs_root *root, WARN_ON(type != TRANS_JOIN && type != TRANS_JOIN_NOLOCK); h = current->journal_info; h->use_count++; + WARN_ON(h->use_count > 2); h->orig_rsv = h->block_rsv; h->block_rsv = NULL; goto got_it; -- 1.7.6.5 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More major...

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use

...al transaction commit. (Alternatively, a failure could branch/jump to another point in the transaction op vector to do some cleanup and/or an explicit WEDGE op to accomplish the same thing?) - This still uses the existing ioctl start transaction call. Depending on how Josef''s ENOSPC journal_info stuff works out, I should be able to avoid the current global open_ioctl_trans counter for a cleaner interaction with the btrfs transaction code. - The data space reservation is still missing. I need a way to find which space_info will be used, and pin it for the duration of the entire transa...

This series adds an initial implementation for scrub. It works quite straightforward. The usermode issues an ioctl for each device in the fs. For each device, it enumerates the allocated device chunks. For each chunk, the contained extents are enumerated and the data checksums fetched. The extents are read sequentially and the checksums verified. If an error occurs (checksum or EIO), a good copy