From: Andrew Morton <email@example.com> To: Ian Kent <firstname.lastname@example.org> Cc: Andrei Vagin <email@example.com>, firstname.lastname@example.org, LKML <email@example.com> Subject: Re: [PATCH] autofs: don't stuck in a loop if vfs_write returns an error Date: Fri, 10 Jun 2016 12:07:20 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On Thu, 09 Jun 2016 09:23:26 +0800 Ian Kent <firstname.lastname@example.org> wrote: > > I was getting ready to send these over to Andrew and found that opendir(3) is > > failing on a number of tests (51 of 230, 9 fails are expected) with 4.6.0. > > > > It's not the patches, yours or mine and it doesn't happen with 4.4.x kernels. > > > > Looks like I'm going to have to bisect to work out what's going on and that > > will > > take a while. > > The regression has been fixed now. > > Al Viro sent a patch for it to Linus yesterday, it's commit e6ec03a25f1 in the > Linux tree. > > I can send my patches to Andrew (after re-testing) but any autofs related > testing of linux.next will need the above commit. > > Andrew, surely this isn't the first time this type of problem has happened, how > is it usually handled, what do I need to do to make this go smoothly? e6ec03a25f1 is in Linus's tree now so everything should be good.
next prev parent reply other threads:[~2016-06-10 19:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-01 5:12 Andrey Vagin 2016-04-01 7:37 ` Ian Kent 2016-05-23 21:50 ` Andrei Vagin 2016-05-24 1:34 ` Ian Kent 2016-05-30 5:52 ` Ian Kent 2016-06-09 1:23 ` Ian Kent 2016-06-09 17:27 ` Andrei Vagin 2016-06-10 8:45 ` Ian Kent 2016-06-10 19:07 ` Andrew Morton [this message] 2016-06-16 7:58 ` Ian Kent 2016-06-16 8:31 Ian Kent
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] autofs: don'\''t stuck in a loop if vfs_write returns an error' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).