Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] autobuilder flock hangs
Date: Mon, 13 Aug 2018 23:28:59 +0200	[thread overview]
Message-ID: <20180813212859.GH7915@scaer> (raw)
In-Reply-To: <20180813231826.31d1d041@windsurf>

Thomas, Hollis, All,

On 2018-08-13 23:18 +0200, Thomas Petazzoni spake thusly:
> Hello,
> 
> +Yann in Cc.
> 
> On Mon, 13 Aug 2018 11:18:10 -0700, Hollis Blanchard wrote:
> 
> > >>        x86_64 |                azure-iot-sdk-c | TIM | http://autobuild.buildroot.net/results/43b9bccacd88397d732fda16d998fa7dc001f900 |  
> > > Hollis: your autobuilder times out when downloading this package, could
> > > you have a look ? See
> > > http://autobuild.buildroot.net/?reason=azure-iot-sdk-c%.  
> > 
> > 
> > >>        xtensa |                 linux-firmware | TIM | http://autobuild.buildroot.net/results/34b8bb8824d369e5b53e2a4effd1a8d18df07aee |  
> > > Hollis, once again your autobuilder timing out when downloading stuff:
> > > http://autobuild.buildroot.net/?reason=linux-firmware%.  
> > flock was hanging. I don't know why; have you experienced anything like 
> > that?
> Not that I remember. Yann ?

Nope.

flock(1) is just a utility wrapper around flock(2), which is itself a
syscall to the kernel. The kernel frees a lock as soon as the process
that aqcquired it closes the filedescriptor(s) used to acquire that
lock, which also automatically occurs when the process dies (naturally
or forcibly).

So, barring a kernel bug, I'd say something else also had a lock...

You can get the list of process haviong locks with the lslocks command.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-08-13 21:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-12  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-11 Thomas Petazzoni
2018-08-12 20:36 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-08-13 11:33   ` Romain Naour
2018-08-13 14:15   ` Matthew Weber
2018-08-13 22:43     ` Arnout Vandecappelle
2018-08-14  2:21       ` Matthew Weber
2018-08-13 14:36   ` Matthew Weber
2018-08-13 15:30     ` Matthew Weber
2018-08-13 18:10       ` [Buildroot] host-libselinux atomics with GCC 4.4 Hollis Blanchard
2018-08-13 18:25         ` Matthew Weber
2018-08-13 19:43           ` Hollis Blanchard
2018-08-16  9:43             ` Thomas Petazzoni
2018-08-13 18:18   ` [Buildroot] autobuilder flock hangs Hollis Blanchard
2018-08-13 21:18     ` Thomas Petazzoni
2018-08-13 21:28       ` Yann E. MORIN [this message]
2018-08-16  9:10     ` Thomas Petazzoni
2018-08-24  7:02       ` [Buildroot] Autobnuilders timeouts [was: Re: autobuilder flock hangs] Yann E. MORIN
2018-08-24 23:45         ` Hollis Blanchard
2018-08-25 13:05           ` Yann E. MORIN
2018-09-27 17:18             ` Hollis Blanchard
2018-08-24 23:54         ` Matthew Weber
2018-08-25 13:31           ` Yann E. MORIN
2018-08-25 13:58             ` Romain Naour
2018-08-26 13:00             ` Matthew Weber
2018-08-27 16:31         ` Julien Boibessot
2018-08-28  9:03           ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180813212859.GH7915@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox