Introduce a new parameter, struct extent_changeset for
btrfs_qgroup_reserved_data() and its callers.
Such extent_changeset was used in btrfs_qgroup_reserve_data() to record
which range it reserved in current reserve, so it can free it at error
path.
The reason we need to export it to callers is,
On Wed, May 17, 2017 at 10:56:27AM +0800, Qu Wenruo wrote:
> Introduce a new parameter, struct extent_changeset for
> btrfs_qgroup_reserved_data() and its callers.
>
> Such extent_changeset was used in btrfs_qgroup_reserve_data() to record
> which range it reserved in current reserve, so it can fr
At 05/17/2017 11:37 PM, David Sterba wrote:
On Wed, May 17, 2017 at 10:56:27AM +0800, Qu Wenruo wrote:
Introduce a new parameter, struct extent_changeset for
btrfs_qgroup_reserved_data() and its callers.
Such extent_changeset was used in btrfs_qgroup_reserve_data() to record
which range it re
On Thu, May 18, 2017 at 08:24:26AM +0800, Qu Wenruo wrote:
> >> +static inline void extent_changeset_init(struct extent_changeset
> >> *changeset)
> >> +{
> >> + changeset->bytes_changed = 0;
> >> + ulist_init(&changeset->range_changed);
> >> +}
> >> +
> >> +static inline struct extent_changeset
At 05/18/2017 09:45 PM, David Sterba wrote:
On Thu, May 18, 2017 at 08:24:26AM +0800, Qu Wenruo wrote:
+static inline void extent_changeset_init(struct extent_changeset *changeset)
+{
+ changeset->bytes_changed = 0;
+ ulist_init(&changeset->range_changed);
+}
+
+static inline struc
On Fri, May 19, 2017 at 08:32:18AM +0800, Qu Wenruo wrote:
> At 05/18/2017 09:45 PM, David Sterba wrote:
> > On Thu, May 18, 2017 at 08:24:26AM +0800, Qu Wenruo wrote:
> +static inline void extent_changeset_init(struct extent_changeset
> *changeset)
> +{
> +changeset->b
At 05/29/2017 11:51 PM, David Sterba wrote:
On Fri, May 19, 2017 at 08:32:18AM +0800, Qu Wenruo wrote:
At 05/18/2017 09:45 PM, David Sterba wrote:
On Thu, May 18, 2017 at 08:24:26AM +0800, Qu Wenruo wrote:
+static inline void extent_changeset_init(struct extent_changeset *changeset)
+{
+
On Wed, May 31, 2017 at 08:31:35AM +0800, Qu Wenruo wrote:
> >> Yes it's hard to find such deadlock especially when lockdep will not
> >> detect it.
> >>
> >> And this makes the advantage of using stack memory in v3 patch more
> >> obvious.
> >>
> >> I didn't realize the extra possible deadlock wh
At 05/31/2017 10:30 PM, David Sterba wrote:
On Wed, May 31, 2017 at 08:31:35AM +0800, Qu Wenruo wrote:
Yes it's hard to find such deadlock especially when lockdep will not
detect it.
And this makes the advantage of using stack memory in v3 patch more obvious.
I didn't realize the extra possi
On Thu, Jun 01, 2017 at 09:01:26AM +0800, Qu Wenruo wrote:
>
>
> At 05/31/2017 10:30 PM, David Sterba wrote:
> > On Wed, May 31, 2017 at 08:31:35AM +0800, Qu Wenruo wrote:
> Yes it's hard to find such deadlock especially when lockdep will not
> detect it.
>
> And this makes th
10 matches
Mail list logo