From: Andrew Morton <akpm@linux-foundation.org>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, Jan Kara <jack@ucw.cz>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: 2.6.26-mmotm-0724 - linux-next.git loses /proc/sys/fs/quota, breaks disk quotas
Date: Sat, 26 Jul 2008 20:25:25 -0700 [thread overview]
Message-ID: <20080726202525.3ac3052f.akpm@linux-foundation.org> (raw)
In-Reply-To: <14615.1217125366@turing-police.cc.vt.edu>
On Sat, 26 Jul 2008 22:22:46 -0400 Valdis.Kletnieks@vt.edu wrote:
> I bisected the problem to somewhere in here:
>
> repeatable-slab-corruption-with-ltp-msgctl08.patch GOOD
> #
> linux-next.patch
> linux-next-git-rejects.patch
> linux-next-fixup.patch BAD
>
> I have no idea how to go bisecting through linux-next.patch
You need to grab the git tree and use git-bisect. Then wade through
all the runtime and compile-time bisection breakage which people
nowadays seem to find acceptable because git collapses in an
ignominious heap when these are fixed.
> It works in 26-mmotm-0715, but is broken in -0724, so that will hopefully
> narrow the suspect commits down a *little* bit...
>
> The problem is that the userspace does this:
>
> /* Detect new kernel interface; Assume generic interface unless we can p
> rove there is not one... */
> if (!stat("/proc/sys/fs/quota", &st) || errno != ENOENT) {
> kernel_iface = IFACE_GENERIC;
> kernel_formats |= (1 << QF_VFSOLD) | (1 << QF_VFSV0);
> }
> else {
> struct v2_dqstats v2_stats;
>
> and /proc/sys/fs/quota has mysteriously vanished in -0724. As a result,
> the userspace code goes looking for the quotav1 files and doesn't find them,
> since the actual files on disk are quotav2 (with a different name).
>
> fs/dquot.c, which contains the code for that, appears to be identical in -0715
> and -0724, so something *else* is breaking it.
>
> Anybody know where /proc/sys/fs/quota went?
>
Nope. There are pretty extensive changes to procfs core in the vfs
tree - perhaps something there made /proc/sys/fs/quota vanish.
<checks>
Yup, it happens in the most recent linux-next too.
Ah, it seems to be taking a little vacation over in
/proc/sys/kernel/. Curious.
next prev parent reply other threads:[~2008-07-27 3:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 2:22 Valdis.Kletnieks
2008-07-27 3:25 ` Andrew Morton [this message]
2008-07-27 3:43 ` Valdis.Kletnieks
2008-07-27 3:50 ` Roland Dreier
2008-07-27 4:09 ` Al Viro
2008-07-27 5:17 ` [PATCH] " Al Viro
2008-07-27 5:31 ` [PATCH] lost sysctl fix Al Viro
2008-07-27 6:29 ` Ingo Molnar
2008-07-27 6:35 ` Ingo Molnar
2008-07-27 6:31 ` Valdis.Kletnieks
2008-07-27 5:53 ` [PATCH] Re: 2.6.26-mmotm-0724 - linux-next.git loses /proc/sys/fs/quota, breaks disk quotas Valdis.Kletnieks
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=20080726202525.3ac3052f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jack@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®