Re: [GIT PULL] Btrfs updates for 4.18

On 06/29/2018 02:26 AM, David Sterba wrote: On Thu, Jun 28, 2018 at 07:22:59PM +0800, Anand Jain wrote: The circular locking dependency warning occurs at FSSTRESS_PROG. And in particular at doproc() in xfstests/ltp/fsstress.c, randomly at any of the command at opdesc_t

Re: [GIT PULL] Btrfs updates for 4.18

On Thu, Jun 28, 2018 at 07:22:59PM +0800, Anand Jain wrote: > The circular locking dependency warning occurs at FSSTRESS_PROG. > And in particular at doproc() in xfstests/ltp/fsstress.c, randomly > at any of the command at > opdesc_tops[] = { ..} > which involves calling mmap

Re: [GIT PULL] Btrfs updates for 4.18

On 06/12/2018 12:16 AM, David Sterba wrote: On Mon, Jun 11, 2018 at 10:50:54AM +0100, Filipe Manana wrote: btrfs: replace uuid_mutex by device_list_mutex in btrfs_open_devices * * the mutex can be very coarse and can cover long-running operations * * protects: updates

Re: [GIT PULL] Btrfs updates for 4.18

On Mon, Jun 11, 2018 at 10:50:54AM +0100, Filipe Manana wrote: > >>>btrfs: replace uuid_mutex by device_list_mutex in > >>> btrfs_open_devices > >> * > >> * the mutex can be very coarse and can cover long-running operations > >> * > >> * protects: updates to fs_devices counters

Re: [GIT PULL] Btrfs updates for 4.18

On Mon, Jun 11, 2018 at 9:14 AM, Anand Jain wrote: > > > On 06/10/2018 12:21 AM, Filipe Manana wrote: >> >> On Mon, Jun 4, 2018 at 4:43 PM, David Sterba wrote: >>> >>> Hi, >>> >>> there are some new features and a usual load of cleanups, more details >>> below. >>> >>> Specifically, there's a

Re: [GIT PULL] Btrfs updates for 4.18

On 06/10/2018 12:21 AM, Filipe Manana wrote: On Mon, Jun 4, 2018 at 4:43 PM, David Sterba wrote: Hi, there are some new features and a usual load of cleanups, more details below. Specifically, there's a set of new non-privileged ioctls to allow subvolume listing. It works but still needs

Re: [GIT PULL] Btrfs updates for 4.18

On Mon, Jun 4, 2018 at 4:43 PM, David Sterba wrote: > Hi, > > there are some new features and a usual load of cleanups, more details below. > > Specifically, there's a set of new non-privileged ioctls to allow > subvolume listing. It works but still needs a security review as it's a > new

[GIT PULL] Btrfs fix for 4.17-rc6

Hi, please consider pulling a fix for btrfs. This time it's really a one-liner and prevents leaking an internal error value 1 out of the ftruncate syscall. This has been observed in practice. The steps to reproduce make a common pattern (open/write/fync/ftruncate) but also need the application

Re: [GIT PULL] Btrfs fixes for 4.17-rc6

On Sun, May 20, 2018 at 8:21 AM David Sterba wrote: > They IMHO qualify for a late rc, though I did not expect that many. Especially with the tree-log.c changes being fairly big, I took a look, and I have to say that I appreciate (a) the warning in the pull request and (b) the

[GIT PULL] Btrfs fixes for 4.17-rc6

Hi, we've accumulated some fixes during the last week, some of them were in the works for a longer time but there are some newer ones too. Most of the fixes have a reproducer and fix user visible problems, also candidates for stable kernels. They IMHO qualify for a late rc, though I did not

[GIT PULL] Btrfs updates for 4.17-rc3

Hi, please pull the following branch with 2 regression fixes and one fix for stable. Thanks. The following changes since commit c0872323746e11fc79344e3738b283a8cda86654: btrfs: print-tree: debugging output enhancement

[GIT PULL] Btrfs fixes for 4.17-rc1

Hi, the branch contains a few fixups to qgroup patches that were merged this dev cycle, unaligned access fix, blockgroup removal corner case fix and a small debugging output tweak. Please pull, thanks. The following changes since

[GIT PULL] Btrfs updates for 4.17, part 2

Hi, we have queued a few more fixes (error handling, log replay, softlockup) and the rest is SPDX update that touches almost all files so the diffstat is long. The top patch is a fixup for excessive warning and was not in linux-next but I've tested it locally. Please pull, thanks.

[GIT PULL] Btrfs updates for 4.17

Hi, please pull the following btrfs changes. There are a several user visible changes, the rest is mostly invisible and continues to clean up the whole code base. There are no merge conflicts with current master. Please pull, thanks. User visible changes: - new mount option nossd_spread

[GIT PULL] Btrfs fixes for 4.16-rc6

Hi, there's an important revert in this pull request that needs to go to stable as it causes a corruption on big endian machines. The other fix is for FIEMAP incorrectly reporting shared extents before a sync and one fix for a crash in raid56. So far we got only one report about the BE

[GIT PULL] Btrfs fixes for 4.16-rc4

Hi, please consider the follwing btrfs updates, there are bugfixes or fixes for user visible behaviour. No merge conflicts. Please pull, thanks. - when NR_CPUS is large, a SRCU structure can significantly inflate size of the main filesystem structure that would not be possible to allocate

[GIT PULL] Btrfs fixes for 4.16-rc1

Hi, we have a few assorted fixes, some of them show up during fstests so I gave them more testing. Please pull, thanks. The following changes since commit 3acbcbfc8f06d4ade2aab2ebba0a2542a05ce90c: btrfs: drop devid as

[GIT PULL] Btrfs for 4.16

Hi, the btrfs updates for this cycle are mostly cleanups with a few raid56 bugfixes and some feature additions. Please pull, thanks. Features or user visible changes: - fallocate: implement zero range mode - avoid losing data raid profile when deleting a device - tree item checker: more

[GIT PULL] Btrfs readdir fix for 4.15

Hi, please consider pulling the fix to 4.15. It's been reported recently that readdir can list stale entries under some conditions. As it is a user visible bug I'd like to get it fix despite we're in the late rc. Thanks. The following changes since commit

[GIT PULL] Btrfs fixes for 4.15-rc7

Hi, we have two more fixes for 4.15, aimed for stable. The leak fix is obvious, the second patch fixes a bug revealed by the refcount API, when it behaves differently than previous atomic_t and reports refs going from 0 to 1 in one case. No merge conflicts. Please pull, thanks. The following

[GIT PULL] Btrfs fixes for 4.15-rc3

Hi, this update contains a few fixes (error handling, quota leak, FUA vs nobarrier mount option). There's one one worth mentioning separately - an off-by-one fix that leads to overwriting first byte of an adjacent page with 0, out of bounds of the memory allocated by an ioctl. This is under a

Re: [GIT PULL] Btrfs fixes for 4.15-rc2

On Wed, Nov 29, 2017 at 02:31:24PM -0800, Linus Torvalds wrote: > On Wed, Nov 29, 2017 at 11:28 AM, David Sterba wrote: > > > > With signed tag: for-4.15-rc2-tag > > > > git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.15-rc2 > > Oh, please actually ask me

Re: [GIT PULL] Btrfs fixes for 4.15-rc2

On Wed, Nov 29, 2017 at 11:28 AM, David Sterba wrote: > > With signed tag: for-4.15-rc2-tag > > git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.15-rc2 Oh, please actually ask me to pull the signed tag (exact same pull-request, just point git request-pull

[GIT PULL] Btrfs fixes for 4.15-rc2

Hi, we've collected some fixes in since the pre-merge window freeze. There's technically only one regression fix for 4.15, but the rest seems important and candidates for stable. No merge conflicts, please pull, thanks. - fix missing flush bio puts in error cases (is serious, but rarely happens)

Re: [GIT PULL] Btrfs changes for 4.15

On Tue, Nov 14, 2017 at 07:39:11AM +0800, Qu Wenruo wrote: > > - extend mount options to specify zlib compression level, -o compress=zlib:9 > > However the support for it has a big problem, it will cause wild memory > access for "-o compress" mount option. > > Kernel ASAN can detect it easily

Re: [GIT PULL] Btrfs changes for 4.15

On 2017年11月13日 23:35, David Sterba wrote: > Hi, > > please pull the following btrfs changes. There are some new user features and > the usual load of invisible enhancements or cleanups. The branch merges > cleanly, has been frozen in case rc7 was the last one, so I send out the pull > request

[GIT PULL] Btrfs changes for 4.15

Hi, please pull the following btrfs changes. There are some new user features and the usual load of invisible enhancements or cleanups. The branch merges cleanly, has been frozen in case rc7 was the last one, so I send out the pull request early. Thanks. New features: - extend mount options to

Re: [GIT PULL] Btrfs fixes for 4.14-rc4

On Fri, Oct 06, 2017 at 11:25:12PM +0100, Tomasz Kłoczko wrote: > On rc3 is possible to observe warning about possible circular locking > dependency which I've reported on btrfs list few days ago: > Thanks for the report, neither this nor the one you reported on rc2 looks like a deadlock to me.

Re: [GIT PULL] Btrfs fixes for 4.14-rc4

On rc3 is possible to observe warning about possible circular locking dependency which I've reported on btrfs list few days ago: [ 101.326724] == [ 101.326728] WARNING: possible circular locking dependency detected [ 101.326734]

[GIT PULL] Btrfs fixes for 4.14-rc4

Hi, we have two more fixes for bugs introduced in 4.13. The sector_t problem with 32bit architecture and !LBDAF config seems serious but the number of affected deployments is hopefully low. The clashing status bits could lead to a confusing in-memory state of the whole-filesystem operations if

[GIT PULL] Btrfs fixes for 4.14-rc3

Hi, we've collected a bunch of isolated fixes, for crashes, user-visible behaviour or missing bits from other subsystem cleanups from the past. The overall number is not small but I was not able to make it significantly smaller. Most of the patches are supposed to go to stable. There are no

[GIT PULL] Btrfs for 4.14

Hi, please pull the following btrfs branch to 4.14. The changes range through all types: cleanups, core chagnes, sanity checks, fixes, other user visible changes, detailed list below. Merging notes: there's a minor conflict with the blk_status_t fix that went to 4.13-rc7 while this pull is on

[GIT PULL] Btrfs fix for rc7

Hi, we have one more fixup that stems from the blk_status_t conversion that did not quite cover everything. The normal cases were not affected because the code is 0, but any error and retries could mix up new and old values. Please pull, thanks.

[GIT PULL] Btrfs fixes for 4.13-rc3

Hi, please pull the following btrfs fixes. They're addressing problems reported by users, and there's one more regression fix. Thanks. The next pull request will be sent by Chris, I'm heading off to vacation. The following changes since commit c3cfb656307583ddfea45375c10183737593c195:

[GIT PULL] Btrfs for 4.13, part 2

Hi, we've identified and fixed a silent corruption (introduced by code in the first pull), a fixup after the blk_status_t merge and two fixes to incremental send that Filipe has been hunting for some time. Please pull, thanks. The

Re: [GIT PULL] Btrfs for 4.13

On Wed, Jul 05, 2017 at 04:45:49PM -0700, Linus Torvalds wrote: > Ouch, yeah, that was annoying. And yes, I ended up with several > whitespace differences but other than that it looks the same. Oh well. > > Jens, Christoph, let's not do that stupid thing with status-vs-error > ever again, ok? It

Re: [GIT PULL] Btrfs for 4.13

On Tue, Jul 4, 2017 at 8:19 AM, David Sterba wrote: > > There are conflicts with the recently merged block layer branch, the > resolutions are a bit tedious but still straightforward. Stephen sent a mail > about that [1]. You can find my merge at for-4.13-part1-merged, there

[GIT PULL] Btrfs for 4.13

Hi, please pull the following btrfs changes. As agreed, the pull request comes from me because Chris is on vacation. The changelog is below. There are conflicts with the recently merged block layer branch, the resolutions are a bit tedious but still straightforward. Stephen sent a mail about

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.12 branch has some fixes that Dave Sterba collected: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.12 We've been hitting an early enospc problem on production machines that Omar tracked down to an old int->u64 mistake. I waited a bit

Re: [GIT PULL] Btrfs

On 05/09/2017 01:56 PM, Chris Mason wrote: > Hi Linus, > > My for-linus-4.12 branch: > > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git > for-linus-4.12 I hit send too soon, sorry. There's a trivial conflict with our WARN_ON fix that went into 4.11. I pushed the

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.12 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.12 Has fixes and cleanups Dave Sterba collected for the merge window. The biggest functional fixes are between btrfs raid5/6 and scrub, and raid5/6 and device replacement. Some

[GIT PULL] Btrfs

Hi Linus, We have one more for btrfs: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.11 This is dropping a new WARN_ON from rc1 that ended up making more noise than we really want. The larger fix for the underflow got delayed a bit and it's better for now

Re: [GIT PULL] Btrfs bug fixes for 4.12

On 04/26/2017 01:52 PM, fdman...@kernel.org wrote: From: Filipe Manana Hi Chris, Please consider the following changes for the 4.12 merge window. These are all bug fixes and nothing particularly outstanding compared to changes for past merge windows. Thanks. The following

[GIT PULL] Btrfs bug fixes for 4.12

From: Filipe Manana Hi Chris, Please consider the following changes for the 4.12 merge window. These are all bug fixes and nothing particularly outstanding compared to changes for past merge windows. Thanks. The following changes since commit

[GIT PULL] Btrfs

Hi Linus Dave Sterba collected a few more fixes for the last rc: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.11 These aren't marked for stable, but I'm putting them in with a batch were testing/sending by hand for this release. Liu Bo (3) commits

[GIT PULL] Btrfs

Hi Linus, We have 3 small fixes queued up in my for-linus-4.11 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.11 Goldwyn Rodrigues (1) commits (+7/-7): btrfs: Change qgroup_meta_rsv to 64bit Dan Carpenter (1) commits (+6/-1): Btrfs: fix an

[GIT PULL] Btrfs

Hi Linus We have a small set of fixes for the next RC: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.11 Zygo tracked down a very old bug with inline compressed extents. I didn't tag this one for stable because I want to do individual tested backports. It's

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.11 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.11 Has Btrfs round two. These are mostly a continuation of Dave Sterba's collection of cleanups, but Filipe also has some bug fixes and performance improvements. Nikolay

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.11 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.11 Has a series of fixes and cleanups that Dave Sterba has been collecting: There is a pretty big variety here, cleaning up internal APIs and fixing corner cases. David Sterba

Re: [GIT PULL] Btrfs bug fixes and improvements for 4.11 (2nd retry)

On Fri, Feb 24, 2017 at 03:25:09AM +, fdman...@kernel.org wrote: From: Filipe Manana Hi Chris, since my previous pull request (sent timely) was either missed or not pulled for some reason I'm not aware of, here I send it again (with one more patch included). The

[GIT PULL] Btrfs bug fixes and improvements for 4.11 (2nd retry)

From: Filipe Manana Hi Chris, since my previous pull request (sent timely) was either missed or not pulled for some reason I'm not aware of, here I send it again (with one more patch included). The following is taken from the former pull request: "Please consider the

[GIT PULL] Btrfs fixes and improvements for 4.11

From: Filipe Manana Hi Chris. Please consider the following changes for the 4.11 merge window. This time there is nothing particularly outstanding when compared to the usual set of bug fixes. These are mostly fixes for send and the no-holes feature introduced in 3.14. Test

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.10 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.10 Has two last minute fixes. The highest priority here is a regression fix for the decompression code, but we also fixed up a problem with the 32 bit compat ioctls. The

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.10 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.10 Has some fixes that we've collected from the list. We still have one more pending to nail down a regression in lzo compression, but I wanted to get this batch out the door.

[GIT PULL] Btrfs fixes

Hi Linus, Dave Sterba queued up a few fixes for btrfs. I have them in my for-linus-4.10 branch: These are all over the place. The tracepoint part of the pull fixes a crash and adds a little more information to two tracepoints, while the rest are good old fashioned fixes.

Re: [GIT PULL] btrfs fixes and cleanups

At 01/13/2017 12:10 AM, Liu Bo wrote: Hi, On Wed, Dec 28, 2016 at 05:30:59PM +0800, Qu Wenruo wrote: Hi Liu, At 12/15/2016 03:13 PM, Liu Bo wrote: Hi David, This is the collection of my patches targetting 4.10, I've dropped patch "Btrfs: adjust len of writes if following a preallocated

Re: [GIT PULL] btrfs fixes and cleanups

Hi, On Wed, Dec 28, 2016 at 05:30:59PM +0800, Qu Wenruo wrote: > Hi Liu, > > At 12/15/2016 03:13 PM, Liu Bo wrote: > > Hi David, > > > > This is the collection of my patches targetting 4.10, I've > > dropped patch "Btrfs: adjust len of writes if following a > > preallocated extent" because of

Re: [GIT PULL] btrfs fixes and cleanups

Hi Liu, At 12/15/2016 03:13 PM, Liu Bo wrote: Hi David, This is the collection of my patches targetting 4.10, I've dropped patch "Btrfs: adjust len of writes if following a preallocated extent" because of the deadlock caused by this commit. Patches are based on v4.9-rc8, and test against

Re: [GIT PULL] btrfs fixes and cleanups

On Wed, Dec 14, 2016 at 11:13:32PM -0800, Liu Bo wrote: > This is the collection of my patches targetting 4.10, I've > dropped patch "Btrfs: adjust len of writes if following a > preallocated extent" because of the deadlock caused by this > commit. > > Patches are based on v4.9-rc8, and test

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.10 branch has our merge window fun: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.10 There is a trivial conflict with your current git, my resolution is here: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git

[GIT PULL] btrfs fixes and cleanups

Hi David, This is the collection of my patches targetting 4.10, I've dropped patch "Btrfs: adjust len of writes if following a preallocated extent" because of the deadlock caused by this commit. Patches are based on v4.9-rc8, and test against fstests with default mount options has been taken to

[GIT PULL] Btrfs fixes for 4.10

From: Filipe Manana Hi Chris, Here follows a small list of fixes a couple cleanups for the 4.10 merge window. It contains all the patches from the previous pull request (which got unanswered nor were the changes pulled yet apparently). The most important change is still the

[GIT PULL] Btrfs corruption fix and a couple cleanups

From: Filipe Manana Hi Chris, Here follows two cleanups and a fix for an issue that leads to a logical corruption in the extent tree, where we end up with file extent items in subvolume trees that don't have a matching extent item and back reference in the extent tree after a

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.9 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.9 Has some fixes that Dave Sterba collected. We held off on these last week because I was focused on the memory corruption testing. I had asked you about pulling this directly

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.9 has two fixes in it: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.9 My patch fixes the btrfs list_head abuse that we tracked down during Dave Jones' memory corruption investigation. With both Jens and my patches in place, I'm no

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.9 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.9 Has some fixes from Omar and Dave Sterba for our new free space tree. This isn't heavily used yet, but as we move toward making it the new default we wanted to nail down an

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.9 has our merge window pull: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.9 This is later than normal because I was tracking down a use-after-free during btrfs/101 in xfstests. I had hoped to fix up the offending patch, but wasn't

[GIT PULL] Btrfs

Hi Linus, We have two fixes in my for-linus-4.8 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.8 Josef is fixing a problem when quotas are enabled with his latest ENOSPC rework, and Jeff is adding more checks into the subvol ioctls to avoid tripping up

[GIT PULL] Btrfs

Hi Linus, We have three fixes in my for-linus-4.8 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.8 I'm not proud of how long it took me to track down that one liner in btrfs_sync_log(), but the good news is the patches I was trying to blame for these

[GIT PULL] Btrfs

Hi Linus, We have a few small fixes queued up in my for-linus-4.8 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.8 I'm still prepping a set of fixes for btrfs fsync, just nailing down a hard to trigger memory corruption. For now, these are tested and

[GIT PULL] Btrfs

Hi Linus, Please pull my for-linus-4.8 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.8 We've queued up a few different fixes in here. These range from enospc corners to fsync and quota fixes, and a few targeted at error handling for corrupt

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.8 branch has some fixes for btrfs send/recv and fsync from Filipe and Robbie Ko: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.8 Bonus points to Filipe for already having xfstests in place for many of these. Filipe Manana (8) commits

[GIT PULL] Btrfs

Hi Linus, This is part two of my btrfs pull, which is some cleanups and a batch of fixes. Most of the code here is from Jeff Mahoney, making the pointers we pass around internally more consistent and less confusing overall. I noticed a small problem right before I sent this out yesterday, so

Re: [GIT PULL] Btrfs fixes for 4.8

On 08/03/2016 06:31 AM, fdman...@kernel.org wrote: From: Filipe Manana Hi Chris, Please consider the following small set of fixes for the 4.8 kernel. These are mostly send fixes, some of them reported and sent by Robbie Ko a long time ago, which I reviewed, updated

[GIT PULL] Btrfs fixes for 4.8

From: Filipe Manana Hi Chris, Please consider the following small set of fixes for the 4.8 kernel. These are mostly send fixes, some of them reported and sent by Robbie Ko a long time ago, which I reviewed, updated (specially the change logs) and tested. All of these already

[GIT PULL] Btrfs

Hi Linus, This is part one of my btrfs pull, and you can find it in my for-linus-4.8 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.8 This pull is dedicated to Josef's enospc rework, which we've been testing for a few releases now. It fixes some early

[GIT PULL] Btrfs

Hi Linus My for-linus-4.7 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.7 Has some fixes and some new self tests for btrfs. The self tests are usually disabled in the .config file (unless you're doing btrfs dev work), and this bunch is meant to find

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.7 branch has some fixes: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.7 I realized as I was prepping this pull that my tip commit still had Facebook task numbers and other internal metadata in it. So I had to reword the description,

[GIT PULL] Btrfs

Hi Linus, We have another round of fixes and a few cleanups in my for-linus-4.7 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.7 I have a fix for short returns from btrfs_copy_from_user, which finally nails down a very hard to find regression we added

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.7 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.7 Has our merge window series of cleanups and fixes. These target a wide range of issues, but do include some important fixes for qgroups, O_DIRECT, and fsync handling. Jeff

[GIT PULL] Btrfs fixes for 4.7

From: Filipe Manana Hi Chris, Please consider the following changes for the merge window for 4.7. There's an implementation for the rename exchange and rename whiteout operations, from Dan Fuhry, which was originally in David's integration branches and linux-next but then we

[GIT PULL] Btrfs

Hi Linus We have some fixes queued up in my for-linus-4.6 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.6 These are bug fixes, including a really old fsync bug, and a few trace points to help us track down problems in the quota code. Mark Fasheh (2)

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.6 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.6 Has a few fixes Dave Sterba had queued up. These are all pretty small, but since they were tested I decided against waiting for more: Alex Lyakas (2) commits (+18/-10):

[GIT PULL] Btrfs file/data loss bug fix

From: Filipe Manana Hi Chris, Please consider the following fix for the linux kernel 4.6 release. It is not a regression in the code for 4.6 nor introduced in any recent release, it's a problem that's been around for a long time (years). But since it's a quite serious one,

Re: [GIT PULL] Btrfs

On Mon, Mar 21, 2016 at 7:24 PM, Chris Mason wrote: > > Hmmm, rereading my answer I realized I didn't actually answer. I really > think this is fixed. I left the warning only because I originally > expected something much more exotic. Ok. It's more that you said the top commit

Re: [GIT PULL] Btrfs

On Mon, Mar 21, 2016 at 10:15:33PM -0400, Chris Mason wrote: > On Mon, Mar 21, 2016 at 06:16:54PM -0700, Linus Torvalds wrote: > > On Mon, Mar 21, 2016 at 5:24 PM, Chris Mason wrote: > > > > > > I waited an extra day to send this one out because I hit a crash late > > > last week

Re: [GIT PULL] Btrfs

On Mon, Mar 21, 2016 at 06:16:54PM -0700, Linus Torvalds wrote: > On Mon, Mar 21, 2016 at 5:24 PM, Chris Mason wrote: > > > > I waited an extra day to send this one out because I hit a crash late > > last week with CONFIG_DEBUG_PAGEALLOC enabled (fixed in the top commit). > > Hmm.

Re: [GIT PULL] Btrfs

On Mon, Mar 21, 2016 at 5:24 PM, Chris Mason wrote: > > I waited an extra day to send this one out because I hit a crash late > last week with CONFIG_DEBUG_PAGEALLOC enabled (fixed in the top commit). Hmm. If that commit helps, it will spit out a warning. So is it actually fixed,

[GIT PULL] Btrfs

Hi Linus, I waited an extra day to send this one out because I hit a crash late last week with CONFIG_DEBUG_PAGEALLOC enabled (fixed in the top commit). Please pull my my for-linus-4.6 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.6 We have a good

[GIT PULL] Btrfs

Hi Linus, We've got a fix in my for-linus-4.5 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.5 Filipe nailed down a problem where tree log replay would do some work that orphan code wasn't expecting to be done yet, leading to BUG_ON. Filipe Manana (1)

Re: [GIT PULL] Btrfs fixes for 4.6

On Wed, Mar 02, 2016 at 09:24:46AM +0800, Qu Wenruo wrote: > > > Chris Mason wrote on 2016/03/01 20:11 -0500: > >On Wed, Mar 02, 2016 at 08:48:06AM +0800, Qu Wenruo wrote: > >> > >> > >>Chris Mason wrote on 2016/03/01 11:06 -0500: > >>>On Tue, Mar 01, 2016 at 10:20:26AM +0100, David Sterba

Re: [GIT PULL] Btrfs fixes for 4.6

Chris Mason wrote on 2016/03/01 20:11 -0500: On Wed, Mar 02, 2016 at 08:48:06AM +0800, Qu Wenruo wrote: Chris Mason wrote on 2016/03/01 11:06 -0500: On Tue, Mar 01, 2016 at 10:20:26AM +0100, David Sterba wrote: Hi Chris, On Fri, Feb 26, 2016 at 01:22:00PM +, fdman...@kernel.org

Re: [GIT PULL] Btrfs fixes for 4.6

On Wed, Mar 02, 2016 at 08:48:06AM +0800, Qu Wenruo wrote: > > > Chris Mason wrote on 2016/03/01 11:06 -0500: > >On Tue, Mar 01, 2016 at 10:20:26AM +0100, David Sterba wrote: > >>Hi Chris, > >> > >>On Fri, Feb 26, 2016 at 01:22:00PM +, fdman...@kernel.org wrote: > >>>The following changes

Re: [GIT PULL] Btrfs fixes for 4.6

Chris Mason wrote on 2016/03/01 11:06 -0500: On Tue, Mar 01, 2016 at 10:20:26AM +0100, David Sterba wrote: Hi Chris, On Fri, Feb 26, 2016 at 01:22:00PM +, fdman...@kernel.org wrote: The following changes since commit 0fcb760afa6103419800674e22fb7f4de1f9670b: Merge branch 'for-next'

Re: [GIT PULL] Btrfs fixes for 4.6

On Tue, Mar 01, 2016 at 10:20:26AM +0100, David Sterba wrote: > Hi Chris, > > On Fri, Feb 26, 2016 at 01:22:00PM +, fdman...@kernel.org wrote: > > The following changes since commit 0fcb760afa6103419800674e22fb7f4de1f9670b: > > > > Merge branch 'for-next' of > >

Re: [GIT PULL] Btrfs fixes for 4.6

Hi Chris, On Fri, Feb 26, 2016 at 01:22:00PM +, fdman...@kernel.org wrote: > The following changes since commit 0fcb760afa6103419800674e22fb7f4de1f9670b: > > Merge branch 'for-next' of > git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux into for-linus-4.6 > (2016-02-24 10:21:44

[GIT PULL] Btrfs fixes for 4.6

From: Filipe Manana Hi Chris, Please consider the following changes for the 4.6 kernel merge window. Nothing particularly outstanding, just the usual sort of bug fixes. These have all been sent to the mailing list before (I just changed in my repo the changelog for the

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.5 branch has a btrfs DIO error passing fix. I know how much you love DIO, so I'm going to suggest against reading it. We'll follow up with a patch to drop the error arg from dio_end_io in the next merge window.

[GIT PULL] Btrfs fix for direct IO error reporting

From: Filipe Manana Hi Chris, Please consider the following fix for an upcoming 4.5 release candidate. It fixes a problem where if the bio for a direct IO request fails, we end reporting success to userspace. For example, for a direct IO write of 64K, if the block layer

[GIT PULL] Btrfs

Hi Linus, Please pull my for-linus-4.5 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.5 This has a few fixes from Filipe, along with a readdir fix from Dave that we've been testing for some time. Filipe Manana (4) commits (+115/-68): Btrfs: remove

  1   2   3   4   5   >