public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: _xfs_buf_ioapply: no ops on block 0x188e78/0x8 on vanilla 4.4.11
Date: Fri, 3 Jun 2016 21:29:56 +0200	[thread overview]
Message-ID: <5751DAB4.40406@applied-asynchrony.com> (raw)
In-Reply-To: <5751C1B9.90709@profihost.ag>

On 06/03/16 19:43, Stefan Priebe - Profihost AG wrote:
> Am 03.06.2016 um 00:25 schrieb Dave Chinner:
>> On Thu, Jun 02, 2016 at 04:21:12PM +0200, Holger Hoffstätte wrote:
>>> On 06/02/16 16:05, Holger Hoffstätte wrote:
>>>> On 06/02/16 15:23, Stefan Priebe - Profihost AG wrote:
>>>>> I found a bug report from redhat here
>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1234586 pointing to this commit:
>>>>> xfs: handle dquot buffer readahead in log recovery correctly
>>>>>
>>>>> which isn't part of 4.4. Is it missing from linux-stable?
>>>>
>>>> Yes, mainline 7d6a13f02356 is missing from 4.4-stable because it applies,
>>>> but doesn't compile. :)
>>>>
>>>> I'll look into a fix.
>>>
>>> Well, that was easy. It also needs 233135b763 ("xfs: print name of verifier
>>> if it fails") which added a .name to the various xfs_buf_ops types.
>>> Can someone confirm that these can both go into 4.4-stable?
>>
>> You could just remove the line:
>>
>> +       .name = "xfs_dquot_ra",
>>
>> from 7d6a13f02356 and that will fix the backport problem and not
>> require any other commits to be backported. I'm fine with either
>> solution.
>>
> 
> Great. Should be push that one to greg?

You're too slow ;-)

http://www.spinics.net/lists/stable/msg134549.html

..or steal them from my patch queue.

-h

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2016-06-03 19:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 13:23 _xfs_buf_ioapply: no ops on block 0x188e78/0x8 on vanilla 4.4.11 Stefan Priebe - Profihost AG
2016-06-02 14:05 ` Holger Hoffstätte
2016-06-02 14:21   ` Holger Hoffstätte
2016-06-02 22:25     ` Dave Chinner
2016-06-02 22:43       ` Holger Hoffstätte
2016-06-03 17:43       ` Stefan Priebe - Profihost AG
2016-06-03 19:29         ` Holger Hoffstätte [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5751DAB4.40406@applied-asynchrony.com \
    --to=holger@applied-asynchrony.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox