Some trivial code cleanups for hostfs.
Signed-off-by: Richard Weinberger
---
fs/hostfs/hostfs_user.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/hostfs/hostfs_user.c b/fs/hostfs/hostfs_user.c
index 6777aa0..68ead6f 100644
--- a/fs/hostfs/hostfs_user.c
+++ b/fs
365b1818 resized f_spare within struct statfs which
caused a UML crash.
There is no need to copy f_spare.
Signed-off-by: Richard Weinberger
Reported-by: Toralf Förster
Tested-by: Toralf Förster
LKML-Reference: <20101019011125.ga3...@lst.de>
---
fs/hostfs/hostfs.h |3 +--
fs/hostfs/hos
Just some few things to check. How is the memory pressure? What resources does
the UML instances use (network, hostfs, cow). Could it be related to a
network-device not being able initialize?
Stian Skjelstad
> no hints? :-/
>
>Am 15.10.2010 11:42, schrieb Felix Antonius Wilhelm Ostmann:
>> We
no hints? :-/
Am 15.10.2010 11:42, schrieb Felix Antonius Wilhelm Ostmann:
> We use UML since 4 years on one host (P4). Now we build another UML-Host
> on a Xeon and all was fine. A week ago we startet the third guest at the
> Xeon Host and after some time the guest was killed from the host (see
>
On Tue, 19 Oct 2010 03:11:25 +0200, Christoph Hellwig
wrote:
> On Mon, Oct 18, 2010 at 01:02:08PM -0700, Andrew Morton wrote:
>> > >
>> > > Is there any reason for hostfs to be playing with the f_spare field at
>> > > all?
>
> No, there is no reason at all. do_statfs is only called by
> hostfs_
