linux-kernel - Re: [PATCH (for 3.15) 0/5] Fix cross rename race window for LSM.

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:	Thu, 1 May 2014 20:58:11 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	jmorris@...ei.org
Cc:	linux-security-module@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH (for 3.15) 0/5] Fix cross rename race window for LSM.

James, would you send this patchset to Linus?
This patchset is expected to go to 3.15 because this is a kind of regression fix.

Tetsuo Handa wrote:
> Miklos Szeredi wrote:
> > On Sat, Apr 19, 2014 at 2:08 PM, Tetsuo Handa
> > <penguin-kernel@...ove.sakura.ne.jp> wrote:
> > > Michael Kerrisk (man-pages) wrote:
> > >> Now that renameat2() is in 3.15, I've taken these changes.
> > >
> > > What!? I didn't know renameat2() goes to 3.15.
> > >
> > > But I assume that renameat2() is not accessible in 3.15, for I can see
> > > "asmlinkage long sys_renameat2(" but don't see "#define __NR_renameat2".
> > 
> > x86 automatically generates __NR_foo entries and syscall tables from
> > arch/x86/syscalls/syscall_*.tbl, which is why you don't find an
> > explicit definition in the git tree.
> > 
> > Thanks,
> > Miklos
> > 
> 
> Oh, I see. Then, I must submit patches for fixing a race window
> caused by commit da1ce067 "vfs: add cross-rename".
> 
> Regards.
> 
--
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/