All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13016] New: When fcntl with F_SETFL is called from vsftpd functions, it hangs during file request from the client
Date: Mon, 22 Jun 2020 04:51:59 +0000	[thread overview]
Message-ID: <bug-13016-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13016

            Bug ID: 13016
           Summary: When fcntl with F_SETFL is called from vsftpd
                    functions, it hangs during file request from the
                    client
           Product: buildroot
           Version: 2020.02.3
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: prabhusannachi at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 8511
  --> https://bugs.busybox.net/attachment.cgi?id=8511&action=edit
This patch allows fcntl with F_SETFL and no filters.

The fcntl function with F_SETFL is called from various portion of the vsftpd to
activate and deactivate block on the file, hangs when client request a file
from the server. This happens when seccomp_sandbox is enabled in the
configuration.
vsftpd version is 3.0.3

Similar issue has been addressed on 3.0.2 and fixed on other distribution.

Reference:
https://build.opensuse.org/package/view_file/SUSE:SLE-12-SP1:GA/vsftpd.2254/vsftpd-enable-fcntl-f_setfl.patch?expand=1

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-06-22  4:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  4:51 bugzilla at busybox.net [this message]
2024-06-15 14:52 ` [Buildroot] [Bug 13016] When fcntl with F_SETFL is called from vsftpd functions, it hangs during file request from the client bugzilla

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=bug-13016-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.