Details

    Description

      I noticed this line in mysql.err:

      2021-09-13 16:11:44 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
      

      However, /tmp is a tmpfs which does support O_TMPFILE. The issue is that mysqld calls open incorrectly:

      [pid 11696] openat(AT_FDCWD, "/tmp", O_RDWR|O_CREAT|O_TRUNC|O_CLOEXEC|O_TMPFILE, 0660) = -1 EINVAL
      [pid 11696] openat(AT_FDCWD, "/tmp/ibMbcqxC", O_RDWR|O_CREAT|O_EXCL|O_CLOEXEC, 0600) = 8
      [pid 11696] unlink("/tmp/ibMbcqxC")     = 0
      

      Either O_CREAT or O_TMPFILE can be specified, but not both at the same time. This effectively makes the O_TMPFILE support dead code.

      Attachments

        Issue Links

          Activity

            fvogt Fabian Vogt created issue -
            danblack Daniel Black made changes -
            Field Original Value New Value
            Assignee Daniel Black [ danblack ]
            danblack Daniel Black made changes -
            Affects Version/s 10.4.21 [ 26030 ]
            danblack Daniel Black made changes -
            Labels not-10.3
            danblack Daniel Black made changes -
            danblack Daniel Black made changes -
            Fix Version/s 10.4.22 [ 26031 ]
            Fix Version/s 10.5.13 [ 26026 ]
            Fix Version/s 10.6.5 [ 26034 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 125024 ] MariaDB v4 [ 159684 ]

            People

              danblack Daniel Black
              fvogt Fabian Vogt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.