Hi,
I've always liked the idea of being able to do writeout directly based on
block number, rather than the valiant but doomed-to-be-suboptimal heuristics
that our current dirty writeout system does, as it is running above the
pagecache and doesn't know about poor file layouts, or interaction
It's time to sanitize prototypes of bdev -open(), -release()
and -ioctl(). This stuff had sat in need to fix for a long time
and there is a bunch of bugs hard to fix without dealing with it.
1) -open() gets inode * and file *. Almost all instances use only
inode-i_bdev
Hi,
sorry for the late reply, I didn't get to it ASAP when you wrote
and then went on vacation.
On Sun, Jul 29, 2007 at 02:42:19PM +0100, Steven Whitehouse wrote:
Something like the following perhaps? I wrote this last night have
given it a very quick test today and it seems to work. It does
On Mon, 27 Aug 2007, Al Viro wrote:
I have the beginning of that series done and the rest mapped out in enough
details to implement it over this week. If somebody has objections,
questions or comments - yell.
From your description, I have no objections - everything sounds good. My
only
This patch adds the killattr inode operation. inodes that have a
killattr operation defined are responsible for properly handling the
ATTR_KILL_SUID and ATTR_KILL_SGID bits within this operation. inodes
that do not have a killattr op will instead use standard logic which
turns these bits into a
When an unprivileged process attempts to modify a file that has the
setuid or setgid bits set, the VFS will attempt to clear these bits. The
VFS will set the ATTR_KILL_SUID or ATTR_KILL_SGID bits in the ia_valid
mask, and then call notify_change to clear these bits and set the mode
accordingly.
Add the nfs_killattr inode operation. For NFS, we generally want the server
to handle clearing these bits. So the function is really just a noop.
Signed-off-by: Jeff Layton [EMAIL PROTECTED]
---
fs/nfs/dir.c |3 +++
fs/nfs/file.c |2 ++
fs/nfs/inode.c | 10
..make it just clear the ATTR_KILL_S*ID bits since we want the
server to handle it.
Signed-off-by: Jeff Layton [EMAIL PROTECTED]
---
fs/cifs/cifsfs.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/fs/cifs/cifsfs.c b/fs/cifs/cifsfs.c
index cabb6a5..c357c55 100644
This updates the VFS docs under the Documentation/ directory to describe
the new killattr inode operation.
Signed-off-by: Jeff Layton [EMAIL PROTECTED]
---
Documentation/filesystems/Locking |2 ++
Documentation/filesystems/vfs.txt |6 ++
2 files changed, 8 insertions(+), 0
Say Evgeniy, something I was curious about but forgot to ask you
earlier...
On Wednesday 08 August 2007 03:17, Evgeniy Polyakov wrote:
...All oerations are not atomic, since we do not care about precise
number of bios, but a fact, that we are close or close enough to the
limit.
... in
On Mon, Aug 27, 2007 at 11:30:53AM +0100, Al Viro wrote:
3) -ioctl(). What a mess...
Yup.
See also:
Subject: [PATCH] dm: support ioctls on mapped devices: fix with fake file
http://uwsg.indiana.edu/hypermail/linux/kernel/0606.2/2979.html
and related threads.
First of all, we have 3
On Monday August 27, [EMAIL PROTECTED] wrote:
* a bug (AFAICT) in md.c - we open raid components r/w and if it
fails, it fails. Good for our purposes, but... how about raid0 on read-only
devices? In any case, we have a ready place to store mode_t, so it's not a
problem for getting the
The stable util-linux-ng 2.13 release is available at:
ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/
A few numbers:
- 8 months (grr...)
- 368 patches (wow...)
- 35 contributors (thanks...!)
Feedback and bug reports, as always, are welcomed.
Karel
Util-linux-ng
Jeff Layton wrote:
On Tue, 21 Aug 2007 17:21:28 -0400
Josef Sipek [EMAIL PROTECTED] wrote:
On Tue, Aug 21, 2007 at 07:35:51AM -0400, Jeff Layton wrote:
On Tue, 21 Aug 2007 15:35:08 +1000
Timothy Shimmin [EMAIL PROTECTED] wrote:
Jeff Layton wrote:
This should fix all of the filesystems in
14 matches
Mail list logo
