On 09/23/2013 07:41 PM, J. Bruce Fields wrote:
> On Sun, Sep 22, 2013 at 06:58:29PM +0200, Toralf Förster wrote:
>> On 09/10/2013 04:09 PM, J. Bruce Fields wrote:
>>> On Sat, Sep 07, 2013 at 10:44:00PM +0200, Toralf Förster wrote:
Today I run latest git tree with a patched UML (this patch + on
On Sun, Sep 22, 2013 at 06:58:29PM +0200, Toralf Förster wrote:
> On 09/10/2013 04:09 PM, J. Bruce Fields wrote:
> > On Sat, Sep 07, 2013 at 10:44:00PM +0200, Toralf Förster wrote:
> >> Today I run latest git tree with a patched UML (this patch + one for xterm
> >> issues) and got 2 times a core d
On 09/10/2013 04:09 PM, J. Bruce Fields wrote:
> On Sat, Sep 07, 2013 at 10:44:00PM +0200, Toralf Förster wrote:
>> Today I run latest git tree with a patched UML (this patch + one for xterm
>> issues) and got 2 times a core dump
>> when I fuzzy test an UML machine with a nearly identical scenario
On 09/10/2013 04:09 PM, J. Bruce Fields wrote:
> On Sat, Sep 07, 2013 at 10:44:00PM +0200, Toralf Förster wrote:
>> Today I run latest git tree with a patched UML (this patch + one for xterm
>> issues) and got 2 times a core dump
>> when I fuzzy test an UML machine with a nearly identical scenario
On Sat, Sep 07, 2013 at 10:44:00PM +0200, Toralf Förster wrote:
> Today I run latest git tree with a patched UML (this patch + one for xterm
> issues) and got 2 times a core dump
> when I fuzzy test an UML machine with a nearly identical scenario as already
> described but just shutdowned
> both
On Sat, Sep 7, 2013 at 10:44 PM, Toralf Förster wrote:
> Today I run latest git tree with a patched UML (this patch + one for xterm
> issues) and got 2 times a core dump
> when I fuzzy test an UML machine with a nearly identical scenario as already
> described but just shutdowned
> both UML imag
On 08/28/2013 07:21 PM, Toralf Förster wrote:
> On 08/27/2013 08:06 PM, J. Bruce Fields wrote:
>> On Tue, Aug 13, 2013 at 05:53:14PM -0400, bfields wrote:
>>> On Mon, Aug 12, 2013 at 04:36:40PM +0200, Jan Kara wrote:
On Sun 11-08-13 11:48:49, Toralf Förster wrote:
> so that the server eith
Am 02.09.2013 18:53, schrieb Toralf Förster:
> On 09/01/2013 11:15 PM, Richard Weinberger wrote:
>> Am 01.09.2013 18:09, schrieb Toralf Förster:
>>> On 08/30/2013 04:36 PM, Richard Weinberger wrote:
Am 30.08.2013 16:10, schrieb Toralf Förster:
> On 08/29/2013 03:30 PM, J. Bruce Fields wrot
On 09/01/2013 11:15 PM, Richard Weinberger wrote:
> Am 01.09.2013 18:09, schrieb Toralf Förster:
>> On 08/30/2013 04:36 PM, Richard Weinberger wrote:
>>> Am 30.08.2013 16:10, schrieb Toralf Förster:
On 08/29/2013 03:30 PM, J. Bruce Fields wrote:
> On Thu, Aug 29, 2013 at 11:57:45AM +0200,
Am 01.09.2013 18:09, schrieb Toralf Förster:
> On 08/30/2013 04:36 PM, Richard Weinberger wrote:
>> Am 30.08.2013 16:10, schrieb Toralf Förster:
>>> On 08/29/2013 03:30 PM, J. Bruce Fields wrote:
On Thu, Aug 29, 2013 at 11:57:45AM +0200, richard -rw- weinberger wrote:
> On Wed, Aug 28, 201
On 08/30/2013 04:36 PM, Richard Weinberger wrote:
> Am 30.08.2013 16:10, schrieb Toralf Förster:
>> On 08/29/2013 03:30 PM, J. Bruce Fields wrote:
>>> On Thu, Aug 29, 2013 at 11:57:45AM +0200, richard -rw- weinberger wrote:
On Wed, Aug 28, 2013 at 7:21 PM, Toralf Förster
wrote:
> On
richard -rw- weinberger wrote:
Thanks for the report. I think I see the problem--after this commit
nfs4_set_delegation() failures result in nfs4_put_delegation being
called, but nfs4_put_delegation doesn't free the nfs4_file that has
already been set by alloc_
On Fri, Aug 30, 2013 at 04:10:42PM +0200, Toralf Förster wrote:
> On 08/29/2013 03:30 PM, J. Bruce Fields wrote:
> > On Thu, Aug 29, 2013 at 11:57:45AM +0200, richard -rw- weinberger wrote:
> >> On Wed, Aug 28, 2013 at 7:21 PM, Toralf Förster
> >> wrote:
> >>> On 08/27/2013 08:06 PM, J. Bruce Fie
Am 30.08.2013 16:10, schrieb Toralf Förster:
> On 08/29/2013 03:30 PM, J. Bruce Fields wrote:
>> On Thu, Aug 29, 2013 at 11:57:45AM +0200, richard -rw- weinberger wrote:
>>> On Wed, Aug 28, 2013 at 7:21 PM, Toralf Förster
>>> wrote:
On 08/27/2013 08:06 PM, J. Bruce Fields wrote:
> On Tue
On 08/29/2013 03:30 PM, J. Bruce Fields wrote:
> On Thu, Aug 29, 2013 at 11:57:45AM +0200, richard -rw- weinberger wrote:
>> On Wed, Aug 28, 2013 at 7:21 PM, Toralf Förster
>> wrote:
>>> On 08/27/2013 08:06 PM, J. Bruce Fields wrote:
On Tue, Aug 13, 2013 at 05:53:14PM -0400, bfields wrote:
>
On Thu, Aug 29, 2013 at 11:57:45AM +0200, richard -rw- weinberger wrote:
> On Wed, Aug 28, 2013 at 7:21 PM, Toralf Förster
> wrote:
> > On 08/27/2013 08:06 PM, J. Bruce Fields wrote:
> >> On Tue, Aug 13, 2013 at 05:53:14PM -0400, bfields wrote:
> >>> On Mon, Aug 12, 2013 at 04:36:40PM +0200, Jan
On Wed, Aug 28, 2013 at 7:21 PM, Toralf Förster wrote:
> On 08/27/2013 08:06 PM, J. Bruce Fields wrote:
>> On Tue, Aug 13, 2013 at 05:53:14PM -0400, bfields wrote:
>>> On Mon, Aug 12, 2013 at 04:36:40PM +0200, Jan Kara wrote:
On Sun 11-08-13 11:48:49, Toralf Förster wrote:
> so that the s
On 08/27/2013 08:06 PM, J. Bruce Fields wrote:
> On Tue, Aug 13, 2013 at 05:53:14PM -0400, bfields wrote:
>> On Mon, Aug 12, 2013 at 04:36:40PM +0200, Jan Kara wrote:
>>> On Sun 11-08-13 11:48:49, Toralf Förster wrote:
so that the server either crashes (if it is a user mode linux image) or at
On Tue, Aug 13, 2013 at 05:53:14PM -0400, bfields wrote:
> On Mon, Aug 12, 2013 at 04:36:40PM +0200, Jan Kara wrote:
> > On Sun 11-08-13 11:48:49, Toralf Förster wrote:
> > > so that the server either crashes (if it is a user mode linux image) or
> > > at least its reboot functionality got broken
On 08/13/2013 11:53 PM, J. Bruce Fields wrote:
> On Mon, Aug 12, 2013 at 04:36:40PM +0200, Jan Kara wrote:
>> On Sun 11-08-13 11:48:49, Toralf Förster wrote:
>>> so that the server either crashes (if it is a user mode linux image) or at
>>> least its reboot functionality got broken
>>> - if the NF
On Mon, Aug 12, 2013 at 04:36:40PM +0200, Jan Kara wrote:
> On Sun 11-08-13 11:48:49, Toralf Förster wrote:
> > so that the server either crashes (if it is a user mode linux image) or at
> > least its reboot functionality got broken
> > - if the NFS server is hammered with scary NFS calls using a
On Sun 11-08-13 11:48:49, Toralf Förster wrote:
> so that the server either crashes (if it is a user mode linux image) or at
> least its reboot functionality got broken
> - if the NFS server is hammered with scary NFS calls using a fuzzy tool
> running at a remote NFS client under a non-privilege
so that the server either crashes (if it is a user mode linux image) or at
least its reboot functionality got broken
- if the NFS server is hammered with scary NFS calls using a fuzzy tool running
at a remote NFS client under a non-privileged user id.
It can re reproduced, if
- the NFS s
23 matches
Mail list logo