From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Török Edwin" <edwin@etorok.net>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Johannes Stezenbach <js@sig21.net>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: 4.7.0-rc7 ext4 error in dx_probe
Date: Wed, 17 Aug 2016 16:28:33 -0700 [thread overview]
Message-ID: <20160817232833.GF14651@birch.djwong.org> (raw)
In-Reply-To: <8b8fff2d-5c89-856a-65d2-f6962b875f8f@etorok.net>
On Wed, Aug 17, 2016 at 05:27:25PM +0300, Török Edwin wrote:
> On 2016-08-08 09:28, Darrick J. Wong wrote:
> > On Sun, Aug 07, 2016 at 11:56:34PM -0400, Theodore Ts'o wrote:
> >> On Fri, Aug 05, 2016 at 12:15:48PM -0700, Darrick J. Wong wrote:
> >>>>> [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/ext4/inode.c?id=b47820edd1634dc1208f9212b7ecfb4230610a23
> >>>>
> >>>> I added the patch, rebuilt and rebooted. It will take some time
> >>>> before I'll report back since the issue is so hard to reproduce.
> >>>
> >>> FWIW I could trigger it reliably by running a bunch of directory traversal
> >>> programs simultaneously on the same directory. I have a script that fires
> >>> up multiple mutts pointing to the Maildirs for the high traffic Linux lists.
> >>
> >> Hmm, I wonder if we should request that this patch be backported to
> >> -stable. Darrick, what do you think?
> >
> > Seems like an excellent idea.
>
> Hi,
>
> I see 4.7.1. was released, however before testing it in the changelog I can't
> see the inode.c commit with the checksum fix. Is there another commit that
> would provide an equivalent fix, or is the fix not part of 4.7.1?
There's no 'equivalent' fix; the one we have simply didn't make it
to the stable maintainers before 4.7.1 came out.
(Hey Ted, can you send the patch to ... whomever's in charge of 4.7?)
--D
>
> Best regards,
> --Edwin
next prev parent reply other threads:[~2016-08-17 23:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 10:57 Johannes Stezenbach
2016-07-18 13:38 ` Theodore Ts'o
2016-07-18 14:17 ` Johannes Stezenbach
2016-07-27 11:58 ` Johannes Stezenbach
2016-08-03 14:50 ` Török Edwin
2016-08-05 10:35 ` Johannes Stezenbach
2016-08-05 17:02 ` Darrick J. Wong
2016-08-05 18:11 ` Johannes Stezenbach
2016-08-05 19:15 ` Darrick J. Wong
2016-08-08 3:56 ` Theodore Ts'o
2016-08-08 6:28 ` Darrick J. Wong
2016-08-08 16:08 ` Theodore Ts'o
2016-08-08 16:55 ` Darrick J. Wong
2016-08-08 21:13 ` Török Edwin
2016-08-09 2:37 ` Darrick J. Wong
2016-08-09 7:12 ` Török Edwin
2016-08-17 14:27 ` Török Edwin
2016-08-17 23:28 ` Darrick J. Wong [this message]
2016-08-22 7:33 ` Török Edwin
2016-09-01 16:40 ` Darrick J. Wong
2016-08-17 20:02 ` Johannes Stezenbach
2016-08-18 7:44 ` Török Edwin
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=20160817232833.GF14651@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=edwin@etorok.net \
--cc=js@sig21.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®