Re: opening symlinks with O_CREAT under latest 2.5.74

[Petr Vandrovec]

On Mon, Jul 07, 2003 at 08:49:29PM +0200, Felipe Alfaro Solana wrote:
> On Mon, 2003-07-07 at 17:46, Petr Vandrovec wrote:
> > Hi,
> >   couple of things stopped working on my box
> > where I have /dev/vc/XX as symlinks to /dev/ttyXX, and some
> > things use /dev/vc/XX and some /dev/ttyXX. After last update
> > hour ago things which use /dev/vc/XX stopped working for
> > non-root - they now fail with EACCES error if they attempt
> > to redirect its input or output through '>' or '<>' bash
> > redirection operators:
> > 
> > $ touch /tmp/xx
> > $ ln -s /tmp/xx yy
> > $ cat > yy
> > -bash: yy: Permission denied
> > 
> > Strace says:
> > 
> > [pid  3268] open("yy", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = -1 EACCES (Permission denied)

> >   Currently I suspect Trond's LOOKUP_CONTINUE change in 
> > '[PATCH] Add open intent information to the 'struct nameidata', but I
> > did not tried reverting it yet to find whether it is culprit or no. But
> > other changes than these four from Trond looks completely innocent.

Reverting "[e-mail]|ChangeSet|20030704190606|14242" indeed
fixes problem.

> JFYI, on Red Hat 9, I'm having problems when using "vi" to edit a file
> through a symbolic link. For example, I can't save changes with ":wq!"
> in vi when editing "/etc/grub.conf" on my RHL9 box (which is a symbolic
> link to "/boot/grub/grub.conf").

I think that it is unrelated.
						Petr Vandrovec
						[e-mail]