[0/4,v2] Error condition failure fixes

Message

Josef Bacik Feb. 13, 2020, 3:47 p.m. UTC

v1->v2:
- Fixed the ins.objectid thing Nikolay pointed out, and reworked that patch a
  bit to do the right thing in case of a add_extent_mapping() further down in
  that function as well.

------------------- Original email -----------------------------
I've been running my bpf error injection stress script and been fixing what has
fallen out.  I don't think I've fixed everything yet, but to reduce the noise
from Dave's testing here's the current set of fixes I have.  These are based on
misc-next from late last week, but should apply cleanly to the recent set.
These aren't super important, but will cut down on the noise from things like
generic/019 and generic/475.  Thanks,

Josef

Comments

David Sterba Feb. 18, 2020, 3 p.m. UTC | #1

On Thu, Feb 13, 2020 at 10:47:27AM -0500, Josef Bacik wrote:
> v1->v2:
> - Fixed the ins.objectid thing Nikolay pointed out, and reworked that patch a
>   bit to do the right thing in case of a add_extent_mapping() further down in
>   that function as well.
> 
> ------------------- Original email -----------------------------
> I've been running my bpf error injection stress script and been fixing what has
> fallen out.  I don't think I've fixed everything yet, but to reduce the noise
> from Dave's testing here's the current set of fixes I have.  These are based on
> misc-next from late last week, but should apply cleanly to the recent set.
> These aren't super important, but will cut down on the noise from things like
> generic/019 and generic/475.  Thanks,

The VM with 1G of memory does not complain anymore and completes the
whole fstests. Patchset moved from topic branch to misc-next and despite
the fixes are not considered serious I'll forward them to current rc.
Thanks.