From: "P. Christeas" <p_christ@hol.gr>
To: Christoph Hellwig <hch@lst.de>, "lkml, " <linux-kernel@vger.kernel.org>
Subject: Regression in Autofs, 2.6.15-git
Date: Sat, 14 Jan 2006 02:17:55 +0200 [thread overview]
Message-ID: <200601140217.56724.p_christ@hol.gr> (raw)
I had been testing some other thing in the kernel, when I noticed that the
commit (in Linus' tree) given below makes *autofs4* crash.
It does crash with a hard oops whenever I try to enter a /net/host/... address
in konqueror's location bar.
Is this a known issue or should I provide more information?
commit fc33a7bb9c6dd8f6e4a014976200f8fdabb3a45c
Author: Christoph Hellwig <hch@lst.de>
Date: Mon Jan 9 20:52:17 2006 -0800
[PATCH] per-mountpoint noatime/nodiratime
Turn noatime and nodiratime into per-mount instead of per-sb flags.
After all the preparations this is a rather trivial patch. The mount code
needs to treat the two options as per-mount instead of per-superblock, and
touch_atime needs to be changed to check the new MNT_ flags in addition to
the MS_ flags that are kept for filesystems that are always
noatime/nodiratime but not user settable anymore. Besides that core code
only nfs needed an update because it's leaving atime updates to the server
and thus sets the S_NOATIME flag on every inode, but needs to know whether
it's a real noatime mount for an getattr optimization.
While we're at it I've killed the IS_NOATIME/IS_NODIRATIME macros that
were
only used by touch_atime.
next reply other threads:[~2006-01-14 0:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 0:17 P. Christeas [this message]
2006-01-14 11:34 ` Regression in Autofs, 2.6.15-git Andrew Morton
2006-01-14 11:50 ` P. Christeas
2006-01-14 11:54 ` Andrew Morton
2006-01-14 12:56 ` P. Christeas
2006-01-14 13:17 ` Andrew Morton
2006-01-14 14:01 ` Al Viro
2006-01-14 14:05 ` P. Christeas
2006-01-14 14:28 ` Ian Kent
2006-01-14 15:11 ` P. Christeas
2006-01-14 15:25 ` P. Christeas
2006-01-14 17:06 ` Ian Kent
2006-01-14 17:54 ` P. Christeas
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=200601140217.56724.p_christ@hol.gr \
--to=p_christ@hol.gr \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
/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