21 Oct, 2019

1 commit

  • Bit-spinlocks are problematic on PREEMPT_RT if functions which might sleep
    on RT, e.g. spin_lock(), alloc/free(), are invoked inside the lock held
    region because bit spinlocks disable preemption even on RT.

    A first attempt was to replace state lock with a spinlock placed in struct
    buffer_head and make the locking conditional on PREEMPT_RT and
    DEBUG_BIT_SPINLOCKS.

    Jan pointed out that there is a 4 byte hole in struct journal_head where a
    regular spinlock fits in and he would not object to convert the state lock
    to a spinlock unconditionally.

    Aside of solving the RT problem, this also gains lockdep coverage for the
    journal head state lock (bit-spinlocks are not covered by lockdep as it's
    hard to fit a lockdep map into a single bit).

    The trivial change would have been to convert the jbd_*lock_bh_state()
    inlines, but that comes with the downside that these functions take a
    buffer head pointer which needs to be converted to a journal head pointer
    which adds another level of indirection.

    As almost all functions which use this lock have a journal head pointer
    readily available, it makes more sense to remove the lock helper inlines
    and write out spin_*lock() at all call sites.

    Fixup all locking comments as well.

    Suggested-by: Jan Kara
    Signed-off-by: Thomas Gleixner
    Signed-off-by: Jan Kara
    Cc: "Theodore Ts'o"
    Cc: Mark Fasheh
    Cc: Joseph Qi
    Cc: Joel Becker
    Cc: Jan Kara
    Cc: linux-ext4@vger.kernel.org
    Link: https://lore.kernel.org/r/20190809124233.13277-7-jack@suse.cz
    Signed-off-by: Theodore Ts'o

    Thomas Gleixner
     

02 Nov, 2017

1 commit

  • Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the 'GPL-2.0'
    SPDX license identifier. The SPDX identifier is a legally binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the use cases:
    - file had no licensing information it it.
    - file was a */uapi/* one with no licensing information in it,
    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base worksheet, and did an initial spot review of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately clear with lawyers working with the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:
    - Files considered eligible had to be source code files.
    - Make and config files were included as candidates if they contained >5
    lines of source
    - File already had some variant of a license header in it (even if
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

13 May, 2013

1 commit

  • Commit ae4647fb (jbd2: reduce journal_head size) introduced a
    regression where we occasionally hit panic in
    jbd2_journal_put_journal_head() because of wrong b_jcount. The bug is
    caused by gcc making 64-bit access to 32-bit bitfield and thus
    clobbering b_jcount.

    At least for now, those 8 bytes saved in struct journal_head are not
    worth the trouble with gcc bitfield handling so revert that part of
    the patch.

    Reported-by: EUNBONG SONG
    Reported-by: Tony Luck
    Signed-off-by: Jan Kara
    Signed-off-by: "Theodore Ts'o"

    Jan Kara
     

12 Apr, 2013

1 commit

  • Remove unused t_cow_tid field (ext4 copy-on-write support doesn't seem
    to be happening) and change b_modified and b_jlist to bitfields thus
    saving 8 bytes in the structure.

    Signed-off-by: Jan Kara
    Signed-off-by: "Theodore Ts'o"
    Reviewed-by: Zheng Liu

    Jan Kara
     

14 Mar, 2012

1 commit

  • All accesses to checkpointing entries in journal_head are protected
    by j_list_lock. Thus __jbd2_journal_remove_checkpoint() doesn't really
    need bh_state lock.

    Also the only part of journal head that the rest of checkpointing code
    needs to check is jh->b_transaction which is safe to read under
    j_list_lock.

    So we can safely remove bh_state lock from all of checkpointing code which
    makes it considerably prettier.

    Signed-off-by: Jan Kara
    Signed-off-by: "Theodore Ts'o"

    Jan Kara
     

25 Jul, 2011

1 commit

  • In the definition of struct journal_head, the comment for
    the field "unsigned b_cow_tid" says the field tracks the
    last transaction id in which this buffer has been cowed.

    In the header part of file journal-head.h, it defines
    typedef unsigned int tid_t;
    We should use type tid_t to define transaction id fields.

    Change the field "b_cow_tid" of struct journal_head from
    type unsigned to tid_t.

    Signed-off-by: Wang Sheng-Hui
    Acked-by: Amir Goldstein
    Signed-off-by: Jan Kara

    Wang Sheng-Hui
     

21 Mar, 2011

1 commit

  • The b_cow_tid field will be used by the ext4 snapshots code to store
    the transaction id when the buffer was last cowed.

    Merging this patch to mainline will allow users to test ext4 snapshots
    as a standalone module, without the need to patch and install a
    development kernel.

    On 64bit machines this field uses fills in a padding "hole" and does
    not increase the size of the struct. On a 32bit machine this patch
    increases the size of the struct from 60 to 64 bytes.

    Signed-off-by: Amir Goldstein
    Signed-off-by: "Theodore Ts'o"

    Amir Goldstein
     

06 Jan, 2009

1 commit

  • Filesystems often to do compute intensive operation on some
    metadata. If this operation is repeated many times, it can be very
    expensive. It would be much nicer if the operation could be performed
    once before a buffer goes to disk.

    This adds triggers to jbd2 buffer heads. Just before writing a metadata
    buffer to the journal, jbd2 will optionally call a commit trigger associated
    with the buffer. If the journal is aborted, an abort trigger will be
    called on any dirty buffers as they are dropped from pending
    transactions.

    ocfs2 will use this feature.

    Initially I tried to come up with a more generic trigger that could be
    used for non-buffer-related events like transaction completion. It
    doesn't tie nicely, because the information a buffer trigger needs
    (specific to a journal_head) isn't the same as what a transaction
    trigger needs (specific to a tranaction_t or perhaps journal_t). So I
    implemented a buffer set, with the understanding that
    journal/transaction wide triggers should be implemented separately.

    There is only one trigger set allowed per buffer. I can't think of any
    reason to attach more than one set. Contrast this with a journal or
    transaction in which multiple places may want to watch the entire
    transaction separately.

    The trigger sets are considered static allocation from the jbd2
    perspective. ocfs2 will just have one trigger set per block type,
    setting the same set on every bh of the same type.

    Signed-off-by: Joel Becker
    Cc: "Theodore Ts'o"
    Cc:
    Signed-off-by: Mark Fasheh

    Joel Becker
     

17 Oct, 2008

1 commit


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds