linux-kernel - Re: [PATCH] Add "-e" option to rpc.gssd to allow error on ticket expiry. Try 2 with added man pages.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4EC6E2DE.6050700@calvaedi.com>
Date:	Fri, 18 Nov 2011 23:57:34 +0100
From:	John Hughes <john@...vaedi.com>
To:	Trond Myklebust <Trond.Myklebust@...app.com>
CC:	John Hughes <john@...va.com>, linux-nfs@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add "-e" option to rpc.gssd to allow error on ticket
 expiry. Try 2 with added man pages.

On 11/18/2011 11:38 PM, Trond Myklebust wrote:
> The fact of the matter is that most application writers remain blithely
> oblivious of the need to fsync() as the ext4 people know all to well:
> see the attempts to impose the fully posix-compatible 'data=writeback'
> mode as the default and the catastrophe that occurred when
> 'data=ordered' semantics changed for the rename() syscall. Adding new
> failure modes needs to be done with care, or GNOME will crash and/or
> your word processor _will_ lose your last hour or so of work.
>    
1. It's not a new failure mode.  it's how things worked before 2.6.34
2. My ticket usualy expires in the middle of the night.  I get back in 
the morning and have to reboot the workstation because it's hung.  
Anything left in the wordprocessor is lost.

Before this change I got back in the morning, the unlock screen popped 
up, I entered my password and got a new ticket, everyone was happy.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/