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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 4 Aug 2008 21:50:36 +0200
From:	"Oliver Pinter" <oliver.pntr@...il.com>
To:	"Greg KH" <greg@...ah.com>
Cc:	"Willy Tarreau" <w@....eu>, 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

the fixed patches to get a "(fixed)"  ending

On 8/4/08, Greg KH <greg@...ah.com> wrote:
> On Mon, Aug 04, 2008 at 11:34:44AM -0700, Greg KH wrote:
>> 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.
>
> Ok, I take that back, only half of them are linewrapped :)
>
> But it would be easier for you to just resend them all, as that way I
> know which ones have already been rejected by people much easier and I
> can take the proper ones.
>
> thanks,
>
> greg k-h
>


-- 
Thanks,
Oliver
--
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/