[uml-devel] difference of a shell script versus command line WRT "winch_thread : TIOCSCTTY failed on fd 1 err = 1"

[uml-devel] difference of a shell script versus command line WRT "winch_thread : TIOCSCTTY failed on fd 1 err = 1"

[Toralf Förster]

If I run the following script

$> cat l.sh
#!/bin/sh
#

/usr/local/bin/linux-v3.11-8718-g0fb5ca1 earlyprintk ubda=/home/tfoerste/virtual/uml/n22unst4 ubdb=/mnt/ramdisk/n22unst4_swap eth0=tuntap,tap2,72:ef:3d:5d:d3:db mem=1025M con0=fd:0,fd:1 con=pts umid=uml_n22unst4 rootfstype=ext4


then during start of the UML I get

...
Netdevice 0 (72:ef:3d:5d:d3:db) :
TUN/TAP backend -
winch_thread : TIOCSCTTY failed on fd 1 err = 1
EXT4-fs (ubda): mounted filesystem with ordered data mode. Opts: (null)
...


whereas the command - if directly run in the terminal - don't show that line.
Now I'm wondering what makes the difference and what's the correct way to start an UML.


-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Re: [uml-devel] difference of a shell script versus command line WRT "winch_thread : TIOCSCTTY failed on fd 1 err = 1"

[richard -rw- weinberger]

On Mon, Sep 16, 2013 at 10:04 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
> If I run the following script
>
> $> cat l.sh
> #!/bin/sh
> #
>
> /usr/local/bin/linux-v3.11-8718-g0fb5ca1 earlyprintk ubda=/home/tfoerste/virtual/uml/n22unst4 ubdb=/mnt/ramdisk/n22unst4_swap eth0=tuntap,tap2,72:ef:3d:5d:d3:db mem=1025M con0=fd:0,fd:1 con=pts umid=uml_n22unst4 rootfstype=ext4
>
>
> then during start of the UML I get
>
> ...
> Netdevice 0 (72:ef:3d:5d:d3:db) :
> TUN/TAP backend -
> winch_thread : TIOCSCTTY failed on fd 1 err = 1

Hmm, that's a regression introduced by:
commit 250127216dd6635f5730752d7444bdec992aecb0
Author: Richard Weinberger <richard@nod.at>
Date:   Sun Aug 18 13:30:09 2013 +0200

    um: Run UML in it's own session.

    If UML is not run by a shell it can happen that UML
    will kill unrelated proceses upon a fatal exit because
    it issues a kill(0, ...).
    To prevent such oddities we create a new session in main().

    Reported-and-tested-by: Richard W.M. Jones <rjones@redhat.com>
    Signed-off-by: Richard Weinberger <richard@nod.at>


The winch-thread also has it's own session, this seems to be to an issue.

-- 
Thanks,
//richard

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Re: [uml-devel] difference of a shell script versus command line WRT "winch_thread : TIOCSCTTY failed on fd 1 err = 1"

[Toralf Förster]

On 09/22/2013 08:52 AM, richard -rw- weinberger wrote:
> On Mon, Sep 16, 2013 at 10:04 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
>> If I run the following script
>>
>> $> cat l.sh
>> #!/bin/sh
>> #
>>
>> /usr/local/bin/linux-v3.11-8718-g0fb5ca1 earlyprintk ubda=/home/tfoerste/virtual/uml/n22unst4 ubdb=/mnt/ramdisk/n22unst4_swap eth0=tuntap,tap2,72:ef:3d:5d:d3:db mem=1025M con0=fd:0,fd:1 con=pts umid=uml_n22unst4 rootfstype=ext4
>>
>>
>> then during start of the UML I get
>>
>> ...
>> Netdevice 0 (72:ef:3d:5d:d3:db) :
>> TUN/TAP backend -
>> winch_thread : TIOCSCTTY failed on fd 1 err = 1
> 
> Hmm, that's a regression introduced by:
> commit 250127216dd6635f5730752d7444bdec992aecb0
> Author: Richard Weinberger <richard@nod.at>
> Date:   Sun Aug 18 13:30:09 2013 +0200
> 
>     um: Run UML in it's own session.
> 
>     If UML is not run by a shell it can happen that UML
>     will kill unrelated proceses upon a fatal exit because
>     it issues a kill(0, ...).
>     To prevent such oddities we create a new session in main().
> 
>     Reported-and-tested-by: Richard W.M. Jones <rjones@redhat.com>
>     Signed-off-by: Richard Weinberger <richard@nod.at>
> 
> 
> The winch-thread also has it's own session, this seems to be to an issue.
> 

sure - I can reproduce it with linux-v3.11-8718-g0fb5ca1 , which doesn't contain that commit, or ?

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Re: [uml-devel] difference of a shell script versus command line WRT "winch_thread : TIOCSCTTY failed on fd 1 err = 1"

[Toralf Förster]

On 09/22/2013 10:27 AM, Toralf Förster wrote:
> On 09/22/2013 08:52 AM, richard -rw- weinberger wrote:
>> On Mon, Sep 16, 2013 at 10:04 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
>>> If I run the following script
>>>
>>> $> cat l.sh
>>> #!/bin/sh
>>> #
>>>
>>> /usr/local/bin/linux-v3.11-8718-g0fb5ca1 earlyprintk ubda=/home/tfoerste/virtual/uml/n22unst4 ubdb=/mnt/ramdisk/n22unst4_swap eth0=tuntap,tap2,72:ef:3d:5d:d3:db mem=1025M con0=fd:0,fd:1 con=pts umid=uml_n22unst4 rootfstype=ext4
>>>
>>>
>>> then during start of the UML I get
>>>
>>> ...
>>> Netdevice 0 (72:ef:3d:5d:d3:db) :
>>> TUN/TAP backend -
>>> winch_thread : TIOCSCTTY failed on fd 1 err = 1
>>
>> Hmm, that's a regression introduced by:
>> commit 250127216dd6635f5730752d7444bdec992aecb0
>> Author: Richard Weinberger <richard@nod.at>
>> Date:   Sun Aug 18 13:30:09 2013 +0200
>>
>>     um: Run UML in it's own session.
>>
>>     If UML is not run by a shell it can happen that UML
>>     will kill unrelated proceses upon a fatal exit because
>>     it issues a kill(0, ...).
>>     To prevent such oddities we create a new session in main().
>>
>>     Reported-and-tested-by: Richard W.M. Jones <rjones@redhat.com>
>>     Signed-off-by: Richard Weinberger <richard@nod.at>
>>
>>
>> The winch-thread also has it's own session, this seems to be to an issue.
>>
> 
> sure - I can reproduce it with linux-v3.11-8718-g0fb5ca1 , which doesn't contain that commit, or ?
> 
I'd like to bisect iit,k but as soon as I run something like
$> ./l.sh | tee >logfile>
then the issue vanishes - so I can see it on the command line.
Furthermore I know, that it is not in 3.10.0-08763-g7d3107d, but in
v3.12-rc1-42-gf42bcf1 - but without automation bisecting is not funny.


-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Re: [uml-devel] difference of a shell script versus command line WRT "winch_thread : TIOCSCTTY failed on fd 1 err = 1"

[Richard Weinberger]

Am 22.09.2013 11:20, schrieb Toralf Förster:
> On 09/22/2013 10:27 AM, Toralf Förster wrote:
>> On 09/22/2013 08:52 AM, richard -rw- weinberger wrote:
>>> On Mon, Sep 16, 2013 at 10:04 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
>>>> If I run the following script
>>>>
>>>> $> cat l.sh
>>>> #!/bin/sh
>>>> #
>>>>
>>>> /usr/local/bin/linux-v3.11-8718-g0fb5ca1 earlyprintk ubda=/home/tfoerste/virtual/uml/n22unst4 ubdb=/mnt/ramdisk/n22unst4_swap eth0=tuntap,tap2,72:ef:3d:5d:d3:db mem=1025M con0=fd:0,fd:1 con=pts umid=uml_n22unst4 rootfstype=ext4
>>>>
>>>>
>>>> then during start of the UML I get
>>>>
>>>> ...
>>>> Netdevice 0 (72:ef:3d:5d:d3:db) :
>>>> TUN/TAP backend -
>>>> winch_thread : TIOCSCTTY failed on fd 1 err = 1
>>>
>>> Hmm, that's a regression introduced by:
>>> commit 250127216dd6635f5730752d7444bdec992aecb0
>>> Author: Richard Weinberger <richard@nod.at>
>>> Date:   Sun Aug 18 13:30:09 2013 +0200
>>>
>>>     um: Run UML in it's own session.
>>>
>>>     If UML is not run by a shell it can happen that UML
>>>     will kill unrelated proceses upon a fatal exit because
>>>     it issues a kill(0, ...).
>>>     To prevent such oddities we create a new session in main().
>>>
>>>     Reported-and-tested-by: Richard W.M. Jones <rjones@redhat.com>
>>>     Signed-off-by: Richard Weinberger <richard@nod.at>
>>>
>>>
>>> The winch-thread also has it's own session, this seems to be to an issue.
>>>
>>
>> sure - I can reproduce it with linux-v3.11-8718-g0fb5ca1 , which doesn't contain that commit, or ?
>>
> I'd like to bisect iit,k but as soon as I run something like
> $> ./l.sh | tee >logfile>
> then the issue vanishes - so I can see it on the command line.
> Furthermore I know, that it is not in 3.10.0-08763-g7d3107d, but in
> v3.12-rc1-42-gf42bcf1 - but without automation bisecting is not funny.

Why bisect? Commit 2501272 is the evildoer.
Now I have to find a sane way to fix the kill(0,...) issue without breaking the winch-thread.

Thanks,
//richard

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel