linux-kernel - Re: [stable] [RFC, 2.6.26.2-rc1] NFS: Ensure we call nfs_sb_deactive() after releasing the directory inode

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 Aug 2008 11:34:44 -0700
From:	Greg KH <greg@...ah.com>
To:	Willy Tarreau <w@....eu>
Cc:	oliver.pntr@...il.com, stable@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [stable] [RFC, 2.6.26.2-rc1] NFS: Ensure we call
	nfs_sb_deactive() after releasing the directory inode

On Sat, Aug 02, 2008 at 07:42:20PM +0200, Willy Tarreau wrote:
> Oliver,
> 
> most of your mails are line-wrapped at some locations :
> 
> > diff --git a/fs/nfs/unlink.c b/fs/nfs/unlink.c
> > index 3adf8b2..f089e58 100644
> > --- a/fs/nfs/unlink.c
> > +++ b/fs/nfs/unlink.c
> > @@ -95,10 +95,11 @@ static void nfs_async_unlink_done(struct rpc_task
> > *task, void *calldata)
> ^^^^^^^^
> see here.
> 
> You may have to fix your mailer (or use another one).

{sigh}

Yes, all of these patches are linewrapped.

Now, I can either go through and edit them all by hand and fix them up,
or Oliver can fix his email client to not doing this anymore, saving
everyone time in the future.

I choose the latter.

Oliver, consider all of the patches you just send out as dropped.  Can
you resend the ones that are actually bugfixes, with out being
linewrapped?

thanks,

greg k-h
--
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/