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] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 30 Sep 2013 17:21:07 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Sedat Dilek <sedat.dilek@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Maxim Patlasov <MPatlasov@...allels.com>
Subject: Re: fuse-3.12-fixes?

On Mon, Sep 30, 2013 at 5:13 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Mon, Sep 30, 2013 at 12:20 AM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>>
>> any reasons why these fuse-3.12-fixes did not went into -rc3?
>
> Perhaps because they were never sent to me?
>
> Searching my email archives I see that a pull request went to Al and
> the mailing lists, but not actually to me. I do have a pending pull
> request from Al (which came in after -rc3) but that doesn't contain
> them either. And the "for-linus" branch implies that perhaps somebody
> _iindended_ to send them to me, but somehow missed.

Mea culpa.  I sent it to Al, but didn't create a for_al branch for it,
and Al didn't pull.  I'll send a new pull request after testing the
fuse_dentry_revalidate fixes.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ