Split the fscache initialisation so that /proc/fs/fscache/stats is always
created, if FSCACHE_STATS=y, thereby allowing it to be used if the read
helper is enabled, but not the rest of the caching infrastructure.
Signed-off-by: David Howells
---
fs/fscache/Makefile |3 +
fs/fscache
Allow the cache to add information in /proc/fs/fscache/objects instead of
displaying cookie key and aux data - which can be seen in the cookies file.
Signed-off-by: David Howells
---
fs/cachefiles/content-map.c | 41 +
fs/cachefiles/interface.c
Allow the cache to add information in /proc/fs/fscache/objects instead of
displaying cookie key and aux data - which can be seen in the cookies file.
Signed-off-by: David Howells
---
fs/cachefiles/content-map.c | 41 +
fs/cachefiles/interface.c
Allow the cache to add information in /proc/fs/fscache/objects instead of
displaying cookie key and aux data - which can be seen in the cookies file.
Signed-off-by: David Howells
---
fs/cachefiles/content-map.c | 41 +
fs/cachefiles/interface.c
Committer: Ingo Molnar
CommitterDate: Mon, 07 Oct 2019 13:42:10 +02:00
x86/platform/uv: Add UV Hubbed/Hubless Proc FS Files
Indicate to UV user utilities that UV hubless support is available on
this system via the existing /proc infterface. The current interface is
maintained with the addition of
On 9/10/2019 11:04 PM, Ingo Molnar wrote:
* Mike Travis wrote:
@@ -1596,7 +1687,7 @@ static void __init uv_system_init_hub(vo
uv_nmi_setup();
uv_cpu_init();
uv_scir_register_cpu_notifier();
- proc_mkdir("sgi_uv", NULL);
+ uv_setup_proc_files(0);
This s
* Mike Travis wrote:
> @@ -1596,7 +1687,7 @@ static void __init uv_system_init_hub(vo
> uv_nmi_setup();
> uv_cpu_init();
> uv_scir_register_cpu_notifier();
> - proc_mkdir("sgi_uv", NULL);
> + uv_setup_proc_files(0);
This slipped through previously: platform drivers ha
type)
+{
+ return (uv_hubbed_system & uvtype);
+}
+EXPORT_SYMBOL_GPL(is_uv_hubbed);
+
int is_uv_hubless(int uvtype)
{
return (uv_hubless_system & uvtype);
@@ -1457,6 +1482,68 @@ static void __init build_socket_tables(v
}
}
+/* Setup user proc fs files */
+static int pro
type)
+{
+ return (uv_hubbed_system & uvtype);
+}
+EXPORT_SYMBOL_GPL(is_uv_hubbed);
+
int is_uv_hubless(int uvtype)
{
return (uv_hubless_system & uvtype);
@@ -1457,6 +1482,68 @@ static void __init build_socket_tables(v
}
}
+/* Setup user proc fs files */
+static int pro
type)
+{
+ return (uv_hubbed_system & uvtype);
+}
+EXPORT_SYMBOL_GPL(is_uv_hubbed);
+
int is_uv_hubless(int uvtype)
{
return (uv_hubless_system & uvtype);
@@ -1457,6 +1482,68 @@ static void __init build_socket_tables(v
}
}
+/* Setup user proc fs files */
+static int pro
return (uv_hubbed_system & uvtype);
+}
+EXPORT_SYMBOL_GPL(is_uv_hubbed);
+
int is_uv_hubless(int uvtype)
{
return (uv_hubless_system & uvtype);
@@ -1457,6 +1482,68 @@ static void __init build_socket_tables(v
}
}
+/* Setup user proc fs files */
+static int proc_
return (uv_hubbed_system & uvtype);
+}
+EXPORT_SYMBOL_GPL(is_uv_hubbed);
+
int is_uv_hubless(int uvtype)
{
return (uv_hubless_system & uvtype);
@@ -1457,6 +1482,68 @@ static void __init build_socket_tables(v
}
}
+/* Setup user proc fs files */
+static int proc_
PL(is_uv_hubbed);
+
int is_uv_hubless(int uvtype)
{
return (uv_hubless_system & uvtype);
@@ -1457,6 +1482,68 @@ static void __init build_socket_tables(v
}
}
+/* Setup user proc fs files */
+static int proc_hubbed_show(struct seq_file *file, void *data)
+{
+ seq_prin
type);
+}
+EXPORT_SYMBOL_GPL(is_uv_hubbed);
+
int is_uv_hubless(int uvtype)
{
return (uv_hubless_system & uvtype);
@@ -1457,6 +1482,68 @@ static void __init build_socket_tables(v
}
}
+/* Setup user proc fs files */
+static int proc_hubbed_show(struct seq_file *
> +extern int _is_uv_hubbed(int uvtype);
> +#define is_uv_hubbed _is_uv_hubbed
> +static inline int _is_uv_hubbed(int uv) { return 0; }
> +#define is_uv_hubbed _is_uv_hubbed
Another two instances of these weird indirections..
& uvtype);
+}
+EXPORT_SYMBOL_GPL(_is_uv_hubbed);
+
int _is_uv_hubless(int uvtype)
{
return (uv_hubless_system & uvtype);
@@ -1477,6 +1502,68 @@ static void __init build_socket_tables(v
}
}
+/* Setup user proc fs files */
+static int proc_hubbed_show(struct seq_file
data via
/proc/fs/xfs/xqmstat, once it relies on the offsets marked via macros.
Fix it.
Fixes: 00f4e4f9 xfs: add rmap btree stats infrastructure
Fixes: aafc3c24 xfs: support the XFS_BTNUM_FINOBT free inode btree type
Fixes: 46eeb521 xfs: introduce refcount btree definitions
Signed-off-by: Carlos
() to display garbage data via
/proc/fs/xfs/xqmstat, once it relies on the offsets marked via macros.
Fix it.
Fixes: 00f4e4f9 xfs: add rmap btree stats infrastructure
Fixes: aafc3c24 xfs: support the XFS_BTNUM_FINOBT free inode btree type
Fixes: 46eeb521 xfs: introduce refcount btree definitions
Show all of a server's addresses in /proc/fs/afs/servers, placing the
second plus addresses on padded lines of their own. The current address is
marked with a star.
Signed-off-by: David Howells
---
fs/afs/proc.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --
On 30/12/16 11:24, Cheah Kok Cheong wrote:
This series does trivial cleanup for COMEDI proc fs related stuff.
Cheah Kok Cheong (5):
Staging: comedi: comedi_fops: Avoid orphaned proc entry
Staging: comedi: proc: Change file permission to read only
Staging: comedi: proc: Add __init prefix
This series does trivial cleanup for COMEDI proc fs related stuff.
Cheah Kok Cheong (5):
Staging: comedi: comedi_fops: Avoid orphaned proc entry
Staging: comedi: proc: Change file permission to read only
Staging: comedi: proc: Add __init prefix
Staging: comedi: proc: Add module owner
ct: Re: [PATCH v2 2/2] ALSA: set no sound proc fs for reduced memory
> footprint
>
> At Wed, 27 May 2015 07:40:24 +,
> Jie, Yang wrote:
> >
> > > -Original Message-
> > > From: Takashi Iwai [mailto:ti...@suse.de]
> > > Sent: Wednesday, May 27
lsa-project.org;
> > linux-kernel@vger.kernel.org; Girdwood, Liam R; Zhang, Vivian
> > Subject: Re: [PATCH v2 2/2] ALSA: set no sound proc fs for reduced memory
> > footprint
> >
> > At Wed, 27 May 2015 07:09:24 +,
> > Jie, Yang wrote:
> > >
> > > >
ct: Re: [PATCH v2 2/2] ALSA: set no sound proc fs for reduced memory
> footprint
>
> At Wed, 27 May 2015 07:09:24 +,
> Jie, Yang wrote:
> >
> > > -Original Message-
> > > From: Takashi Iwai [mailto:ti...@suse.de]
> > > Sent: Wednesday, May 27
lsa-project.org;
> > linux-kernel@vger.kernel.org; Girdwood, Liam R; Zhang, Vivian
> > Subject: Re: [PATCH v2 2/2] ALSA: set no sound proc fs for reduced memory
> > footprint
> >
> > At Wed, 27 May 2015 05:38:01 +,
> > Jie, Yang wrote:
> > >
> > > > -
ct: Re: [PATCH v2 2/2] ALSA: set no sound proc fs for reduced memory
> footprint
>
> At Wed, 27 May 2015 05:38:01 +,
> Jie, Yang wrote:
> >
> > > -Original Message-
> > > From: Sudip Mukherjee [mailto:sudipm.mukher...@gmail.com]
> > > Sent:
@alsa-project.org; linux-
> > ker...@vger.kernel.org; Girdwood, Liam R; Zhang, Vivian
> > Subject: Re: [PATCH v2 2/2] ALSA: set no sound proc fs for reduced memory
> > footprint
> >
> > On Tue, May 26, 2015 at 09:13:57PM +0800, Jie Yang wrote:
> > > Disable sou
vian
> Subject: Re: [PATCH v2 2/2] ALSA: set no sound proc fs for reduced memory
> footprint
>
> On Tue, May 26, 2015 at 09:13:57PM +0800, Jie Yang wrote:
> > Disable sound proc fs, when CONFIG_SND_NO_PROC_FS is selected, which
> > can save about 9KB memory size for reducing m
On Tue, May 26, 2015 at 09:13:57PM +0800, Jie Yang wrote:
> Disable sound proc fs, when CONFIG_SND_NO_PROC_FS is selected,
> which can save about 9KB memory size for reducing memory
> footprint purpose.
> ---
missing Signed-off-by.
regards
sudip
--
To unsubscribe from this list: s
Disable sound proc fs, when CONFIG_SND_NO_PROC_FS is selected,
which can save about 9KB memory size for reducing memory
footprint purpose.
---
include/sound/info.h | 8
sound/core/Makefile| 2 +-
sound/core/hwdep.c | 6 +++---
sound/core
Disable sound proc fs, when CONFIG_SND_NO_PROC_FS is selected,
which can save about 9KB memory size for reducing memory
footprint purpose.
---
include/sound/info.h | 8
sound/core/Makefile| 2 +-
sound/core/hwdep.c | 6 +++---
sound/core
per can be NULL or stale. Making the idiom
> > pid_ns->child_reaper->nsproxy a double whammy of problems.
> >
> > Luckily all that needs to happen is to move /proc/fs/nfsfs/servers and
> > /proc/fs/nfsfs/volumes under /proc/net to /proc/net/nfsfs/servers and
> &
the initial process in a pid namespace has started or after the
> initial process in a pid namespace has exited where
> pid_ns->child_reaper can be NULL or stale. Making the idiom
> pid_ns->child_reaper->nsproxy a double whammy of problems.
>
> Luckily all that needs to
_reaper can be NULL or stale. Making the idiom
pid_ns->child_reaper->nsproxy a double whammy of problems.
Luckily all that needs to happen is to move /proc/fs/nfsfs/servers and
/proc/fs/nfsfs/volumes under /proc/net to /proc/net/nfsfs/servers and
/proc/net/nfsfs/volumes and add a symlink fro
_reaper can be NULL or stale. Making the idiom
pid_ns->child_reaper->nsproxy a double whammy of problems.
Luckily all that needs to happen is to move /proc/fs/nfsfs/servers and
/proc/fs/nfsfs/volumes under /proc/net to /proc/net/nfsfs/servers and
/proc/net/nfsfs/volumes and add a symlink from t
r can be NULL or stale. Making the idiom
pid_ns->child_reaper->nsproxy a double whammy of problems.
Luckily all that needs to happen is to move /proc/fs/nfsfs/servers and
/proc/fs/nfsfs/volumes under /proc/net to /proc/net/nfsfs/servers and
/proc/net/nfsfs/volumes and add a symlink from the o
r can be NULL or stale. Making the idiom
pid_ns->child_reaper->nsproxy a double whammy of problems.
Luckily all that needs to happen is to move /proc/fs/nfsfs/servers and
/proc/fs/nfsfs/volumes under /proc/net to /proc/net/nfsfs/servers and
/proc/net/nfsfs/volumes and add a symlink from the o
process in a pid namespace has started or after the
> initial process in a pid namespace has exited where
> pid_ns->child_reaper can be NULL or stale. Making the idiom
> pid_ns->child_reaper->nsproxy a double whammy of problems.
>
> Luckily all that needs to happen is to move /
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > I've replaced exportfs, mountd and nfsd with a newer version and it
> > works now.
>
> What version were you using? I would really like to know.
The system in question was built on a Knoppix release based on Debian
Potato, with updates from Woody
On Tuesday December 5, [EMAIL PROTECTED] wrote:
>
> strace on exportfs shows this:nfsservctl(0x3, 0xbf875824, 0) =
> - -1 ENOMEM
What version of nfs-utils are you running? We haven't been using
nfsservctl(3, ...) on 2.6 kernels for ages - which probably explains
why exp_export() has suf
> Will try your patch tomorrow.
...which does not change anything. (As expected.)
Olaf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
/etc/exports: the access control list for filesystems which may be
exported
# to NFS clients. See exports(5).
/video/rec bigred(rw,sync)
strace on exportfs shows this:nfsservctl(0x3, 0xbf875824, 0) =
- -1 ENOMEM
After that, /proc/fs/nfs/export exists and gives the
p and then immediately shutdown does this error trigger,
it does it have to be up for a while?
Just before shutting down, can you
cat /proc/fs/nfsd/exports
and see if that works? If so, can you show me the contents.
If not, can I see your /etc/exports ??
Thanks,
NeilBrown
This patch fixe
This is 100% reproducible. It hangs exportfs on shutdown.
Dec 4 19:50:13 glotze kernel: BUG: unable to handle kernel NULL pointer
dereference at virtual address 0040
Dec 4 19:50:13 glotze kernel: printing eip:
Dec 4 19:50:13 glotze kernel: c017254a
Dec 4 19:50:13 glotze kernel: *pde = 00
On Wed, Mar 09, 2005 at 11:26:30 +0100, Weber Matthias wrote:
> On Tue, Mar 08, 2005 at 20:05:42 +0100, Weber Matthias wrote:
> >> is there any chance to signal an EOF when writing data to kernel via proc
> >> fs? >> Actually if the length of data is N*P
On Tue, Mar 08, 2005 at 20:05:42 +0100, Weber Matthias wrote:
>> is there any chance to signal an EOF when writing data to kernel via proc
>> fs? >> Actually if the length of data is N*PAGE_SIZE it seems not to be
>> detectable.
>> I followed up the "struct fi
On Tue, Mar 08, 2005 at 20:05:42 +0100, Weber Matthias wrote:
> is there any chance to signal an EOF when writing data to kernel via proc fs?
> Actually if the length of data is N*PAGE_SIZE it seems not to be detectable.
> I followed up the "struct file" but haven't fo
Hi,
is there any chance to signal an EOF when writing data to kernel via proc fs?
Actually if the length of data is N*PAGE_SIZE it seems not to be detectable. I
followed up the "struct file" but haven't found anything that helped...
Any help would be appreciated!
Bye
On 03.04, Trond Myklebust wrote:
> fr den 04.03.2005 Klokka 11:58 (+) skreiv J.A. Magallon:
>
> > ===== /proc/fs/nfs/exports
> > # Version 1.1
> > # Path Client(Flags) # IPs
> >
> > Nothing in xtab ? Nothing in /proc ? Why ?
> >
>
> &qu
fr den 04.03.2005 Klokka 11:58 (+) skreiv J.A. Magallon:
> = /proc/fs/nfs/exports
> # Version 1.1
> # Path Client(Flags) # IPs
>
> Nothing in xtab ? Nothing in /proc ? Why ?
>
"man exportfs". Read all about the 2.6 kernel's new mechanism for
communicat
== /var/lib/nfs/xtab"
cat /var/lib/nfs/xtab
echo "===== /proc/fs/nfs/exports"
cat /proc/fs/nfs/exports
Results are:
Stopping NFS statd: [ OK ]
Shutting down NFS mountd:
pranay pramod345678 wrote:
Hi,
i tried for the latest versionof the /proc fs
document supposed to be available online at
http://skaro.nightcrawler.com/~bb/Docs/Proc but
couldn't get it.
can i get some help in this regard ?
> Hi,
Try
http://kernelnewbies.org/documents/kdo
Hi,
i tried for the latest versionof the /proc fs
document supposed to be available online at
http://skaro.nightcrawler.com/~bb/Docs/Proc but
couldn't get it.
can i get some help in this regard ?
thanks.
-pranay
=
Pranay Pramod
Army Institute of Technology
Dighi Hills
Pu
The following patch extends the proc fs api as discussed in the thread "/proc
format" last month (http://marc.theaimsgroup.com/?t=9882254507&w=2&r=1).
It adds the following features:
- dynamic directories. Enables you to use directories for enumerations,
similar
hi all,
please help me to know how the proc file system is
created/implemented.
What are the source files,documentation related?
thanks in advance
bye
srinivas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Hello,
actually the question is in subj.
Problem is that there is a program which needs to know physical memory
size. This information is used to justify memory consumption as after some
swapping performance is drops dramatically, and it is better to finish.
I know that this is not the best idea
Ricky Beam wrote:
>
> On Thu, 14 Sep 2000, Nick Pollitt wrote:
> ...
> >And second, why is the 4K limit there in the first place?
>
> Primarily because it was never designed for 90% of the crap that's in there
> now. I have long hated the BS required to get more than 4k worth of stuff
> out of
On Thu, 14 Sep 2000, Nick Pollitt wrote:
...
>And second, why is the 4K limit there in the first place?
Primarily because it was never designed for 90% of the crap that's in there
now. I have long hated the BS required to get more than 4k worth of stuff
out of /proc. The way around the limit is
On Thu, Sep 14, 2000 at 12:01:49PM -0700, Nick Pollitt wrote:
> I have a machine with many partitions, and /proc/partitions, being
> limited to 4K output, doesn't display all the information I need.
>
> My first question/request is has anyone else already written a patch to
> get around the 4K li
I have a machine with many partitions, and /proc/partitions, being limited to 4K
output, doesn't display all the information I need.
My first question/request is has anyone else already written a patch to get around the
4K limit?
And second, why is the 4K limit there in the first place?
Thank
60 matches
Mail list logo
