Lines Matching refs:you
12 how you decide to allocate the physical media on which the journal
16 journal_t is a typedef for a struct pointer, so when you are finally
17 finished make sure you call :c:func:`jbd2_journal_destroy` on it to free up
20 Once you have got your journal_t object you need to 'mount' or load the
23 When loading the journal you must call :c:func:`jbd2_journal_load` to process
30 :c:func:`jbd2_journal_skip_recovery` for you if it detects any outstanding
35 Now you can go ahead and start modifying the underlying filesystem.
39 by wrapping them into transactions. Additionally you also need to wrap
41 so it knows what the modifications you are actually making are. To do
45 which indicates the end of a transaction are nestable calls, so you can
46 reenter a transaction if necessary, but remember you must call
52 Inside each transaction you need to wrap the modifications to the
53 individual buffers (blocks). Before you start to modify a buffer you
59 uncommitted transaction. At this point you are at last ready to modify a
60 buffer, and once you are have done so you need to call
61 :c:func:`jbd2_journal_dirty_metadata`. Or if you've asked for access to a
62 buffer you now know is now longer required to be pushed back on the
63 device you can call :c:func:`jbd2_journal_forget` in much the same way as you
69 Then at umount time , in your :c:func:`put_super` you can then call
75 until the outermost :c:func:`jbd2_journal_stop`. This means you must complete
76 the transaction at the end of each file/inode/address etc. operation you
87 deadlocks you must treat :c:func:`jbd2_journal_start` /
91 behaviour to :c:func:`jbd2_journal_start` so you can deadlock here just as
95 be the maximum number of blocks you are going to touch in this
100 strategy. Why? Because, if you do a delete, you need to ensure you
102 these blocks commits. If you reused these blocks and crash happens,
109 With journal commit callbacks you can ask the journalling layer to call
111 so that you can do some of your own management. You ask the journalling
132 if you allow unprivileged userspace to trigger codepaths containing
146 of the structures used. As a client of the JBD2 layer you can just rely