At 02/03/2017 01:08 PM, Christoph Anton Mitterer wrote:
Hey Qu.
I'm sending this off-list for privacy reasons of the contained file-
names / hash sums.
It doesn't contained anything particularly secret, nevertheless, please
try to avoid spreading it too far around and delete it once you
This introduces a new helper which can be used to process pages bits.
Signed-off-by: Liu Bo
---
fs/btrfs/extent_io.c | 37 ++---
1 file changed, 22 insertions(+), 15 deletions(-)
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
Since we have a helper to set page bits, let lock_delalloc_pages and
__unlock_for_delalloc use it.
Signed-off-by: Liu Bo
---
fs/btrfs/extent_io.c | 122 ++-
fs/btrfs/extent_io.h | 3 +-
2 files changed, 54 insertions(+), 71
On 02/02/2017 03:57 PM, Greg KH wrote:
> On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote:
>> On 02/02/2017 01:23 PM, Greg KH wrote:
>>> On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
Hello,
Please consider reverting commit
On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote:
> On 02/02/2017 01:23 PM, Greg KH wrote:
> > On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
> >> Hello,
> >>
> >> Please consider reverting commit
> >> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y
On 02/02/2017 01:23 PM, Greg KH wrote:
> On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
>> Hello,
>>
>> Please consider reverting commit
>> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
> What release can I remove it from?
>
> It isn't in 4.4.y, and 4.9.y
On Thu, Feb 02, 2017 at 11:11:15AM -0800, Liu Bo wrote:
> On Thu, Feb 02, 2017 at 07:42:43PM +0100, David Sterba wrote:
> > On Mon, Jan 30, 2017 at 12:26:30PM -0800, Liu Bo wrote:
> > > This creates a helper to manipulate page bits to avoid duplicate uses.
> >
> > This seems too short for what
Hi,
On Thu, Feb 02, 2017 at 06:34:02PM +0100, Jan Kara wrote:
> Provide helper functions for setting up dynamically allocated
> backing_dev_info structures for filesystems and cleaning them up on
> superblock destruction.
Just one concern, will this cause problems for multiple superblock cases
On Thu, Feb 02, 2017 at 07:42:43PM +0100, David Sterba wrote:
> On Mon, Jan 30, 2017 at 12:26:30PM -0800, Liu Bo wrote:
> > This creates a helper to manipulate page bits to avoid duplicate uses.
>
> This seems too short for what the patch does. It adds a new page ops bit
> that would deserve a
On Thu, Feb 02, 2017 at 05:56:33PM +, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> At close_ctree() we free the block groups and then only after we wait for
> any running worker kthreads to finish and shutdown the workqueues. This
> behaviour is racy and it
On Thu, Feb 02, 2017 at 06:58:03PM +, Filipe Manana wrote:
> On Thu, Feb 2, 2017 at 6:53 PM, Liu Bo wrote:
> > On Thu, Feb 02, 2017 at 06:32:01PM +, Filipe Manana wrote:
> >> On Thu, Feb 2, 2017 at 6:19 PM, Liu Bo wrote:
> >> > On Wed, Feb 01,
On Thu, Feb 2, 2017 at 6:53 PM, Liu Bo wrote:
> On Thu, Feb 02, 2017 at 06:32:01PM +, Filipe Manana wrote:
>> On Thu, Feb 2, 2017 at 6:19 PM, Liu Bo wrote:
>> > On Wed, Feb 01, 2017 at 11:01:28PM +, fdman...@kernel.org wrote:
>> >> From: Filipe
On Thu, Feb 02, 2017 at 06:32:01PM +, Filipe Manana wrote:
> On Thu, Feb 2, 2017 at 6:19 PM, Liu Bo wrote:
> > On Wed, Feb 01, 2017 at 11:01:28PM +, fdman...@kernel.org wrote:
> >> From: Filipe Manana
> >>
> >> At close_ctree() we free the block
On Mon, Jan 30, 2017 at 12:26:30PM -0800, Liu Bo wrote:
> This creates a helper to manipulate page bits to avoid duplicate uses.
This seems too short for what the patch does. It adds a new page ops bit
that would deserve a separate patch. Please try to split it to smaller
parts.
> +static
On Thu, Feb 2, 2017 at 6:19 PM, Liu Bo wrote:
> On Wed, Feb 01, 2017 at 11:01:28PM +, fdman...@kernel.org wrote:
>> From: Filipe Manana
>>
>> At close_ctree() we free the block groups and then only after we wait for
>> any running worker kthreads to
On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
> Hello,
>
> Please consider reverting commit
> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
What release can I remove it from?
It isn't in 4.4.y, and 4.9.y doesn't make much sense, unless it's
reverted in
On Wed, Feb 01, 2017 at 11:01:28PM +, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> At close_ctree() we free the block groups and then only after we wait for
> any running worker kthreads to finish and shutdown the workqueues. This
> behaviour is racy and it
On Mon, Jan 30, 2017 at 12:25:28PM -0800, Liu Bo wrote:
> run_delalloc_nocow has used trans in two places where they don't actually need
> @trans.
>
> For btrfs_lookup_file_extent, we search for file extents without COWing
> anything, and for btrfs_cross_ref_exist, the only place where we need
From: Filipe Manana
At close_ctree() we free the block groups and then only after we wait for
any running worker kthreads to finish and shutdown the workqueues. This
behaviour is racy and it triggers an assertion failure when freeing block
groups because while we are doing it
Hello,
this patch series converts all embedded occurences of struct backing_dev_info
to use standalone dynamically allocated structures. This makes bdi handling
unified across all bdi users and generally removes some boilerplate code from
filesystems setting up their own bdi. It also allows us to
On Mon, Jan 30, 2017 at 12:24:37PM -0800, Liu Bo wrote:
> All we need is @delayed_refs, all callers have get it ahead of calling
> btrfs_find_delayed_ref_head since lock needs to be acquired firstly, there is
> no reason to deference it again inside the function.
>
> Signed-off-by: Liu Bo
Hello,
Please consider reverting commit
4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release. It
was included upstream as of v4.7-rc1 This commit introduced a
regression, described in the following bug:
http://bugs.launchpad.net/bugs/1619918
This new regression was discussed in
On Mon, Jan 30, 2017 at 12:23:42PM -0800, Liu Bo wrote:
> @trans is not used at all, this removes it.
>
> Signed-off-by: Liu Bo
Reviewed-by: David Sterba
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message
Allocate struct backing_dev_info separately instead of embedding it
inside superblock. This unifies handling of bdi among users.
CC: Chris Mason
CC: Josef Bacik
CC: David Sterba
CC: linux-btrfs@vger.kernel.org
Signed-off-by: Jan Kara
Provide helper functions for setting up dynamically allocated
backing_dev_info structures for filesystems and cleaning them up on
superblock destruction.
CC: linux-...@lists.infradead.org
CC: linux-...@vger.kernel.org
CC: Petr Vandrovec
CC: linux-ni...@vger.kernel.org
CC:
On 2017-02-02 09:25, Adam Borowski wrote:
On Thu, Feb 02, 2017 at 07:49:50AM -0500, Austin S. Hemmelgarn wrote:
This is a severe bug that makes a not all that uncommon (albeit bad) use
case fail completely. The fix had no dependencies itself and
I don't see what's bad in mounting a RAID
On Thu, Feb 02, 2017 at 07:49:50AM -0500, Austin S. Hemmelgarn wrote:
> This is a severe bug that makes a not all that uncommon (albeit bad) use
> case fail completely. The fix had no dependencies itself and
I don't see what's bad in mounting a RAID degraded. Yeah, it provides no
redundancy but
On 2017-02-02 05:52, Graham Cobb wrote:
On 02/02/17 00:02, Duncan wrote:
If it's a workaround, then many of the Linux procedures we as admins and
users use every day are equally workarounds. Setting 007 perms on a dir
that doesn't have anything immediately security vulnerable in it, simply
to
On 2017-02-01 17:48, Duncan wrote:
Adam Borowski posted on Wed, 01 Feb 2017 12:55:30 +0100 as excerpted:
On Wed, Feb 01, 2017 at 05:23:16AM +, Duncan wrote:
Hans Deragon posted on Tue, 31 Jan 2017 21:51:22 -0500 as excerpted:
But the current scenario makes it difficult for me to put
On Sunday 28 August 2016 15:29:08 Kai Krakow wrote:
> Hello list!
Hi list
> It happened again. While using VirtualBox the following crash happened,
> btrfs check found a lot of errors which it couldn't repair. Earlier
> that day my system crashed which may already introduced errors into my
>
On 02/02/17 00:02, Duncan wrote:
> If it's a workaround, then many of the Linux procedures we as admins and
> users use every day are equally workarounds. Setting 007 perms on a dir
> that doesn't have anything immediately security vulnerable in it, simply
> to keep other users from even
Signed-off-by: Lakshmipathi.G
---
tests/fsck-tests/026-check-inode-link/test.sh | 30 +++
1 file changed, 30 insertions(+)
create mode 100755 tests/fsck-tests/026-check-inode-link/test.sh
diff --git
32 matches
Mail list logo