From: Mimi Zohar <zohar@linux.ibm.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>,
syzbot+ae82084b07d0297e566b@syzkaller.appspotmail.com
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
syzkaller-bugs@googlegroups.com, linux-integrity@vger.kernel.org,
linux-unionfs@vger.kernel.org, amir73il@gmail.com
Subject: Re: [PATCH] IMA: Mask O_RDWR if FMODE_READ is set
Date: Tue, 27 Nov 2018 07:05:09 -0500 [thread overview]
Message-ID: <1543320309.3902.137.camel@linux.ibm.com> (raw)
In-Reply-To: <20181126163847.xy3acvltyeb75nb4@merlin>
On Mon, 2018-11-26 at 10:38 -0600, Goldwyn Rodrigues wrote:
> A file can be opened with open(O_WRONLY | O_RDWR), so a FMORE_READ
> will not be set, and overlayfs will consider another copy_up() on the same
> file leading to a deadlock on mnt_want_write(). Fix it by masking
> O_RDWR while opening the file in read-only mode.
Shouldn't the open itself fail if both O_WRONLY and O_RDWR are
specified?
Mimi
>
>
> Reported-by: syzbot+ae82084b07d0297e566b@syzkaller.appspotmail.com
> Fixes: a408e4a86b36 ("ima: open a new file instance if no read permissions")
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
>
> diff --git a/security/integrity/ima/ima_crypto.c b/security/integrity/ima/ima_crypto.c
> index d9e7728027c6..2efa04e47ff0 100644
> --- a/security/integrity/ima/ima_crypto.c
> +++ b/security/integrity/ima/ima_crypto.c
> @@ -422,7 +422,7 @@ int ima_calc_file_hash(struct file *file, struct ima_digest_data *hash)
> /* Open a new file instance in O_RDONLY if we cannot read */
> if (!(file->f_mode & FMODE_READ)) {
> int flags = file->f_flags & ~(O_WRONLY | O_APPEND |
> - O_TRUNC | O_CREAT | O_NOCTTY | O_EXCL);
> + O_RDWR | O_TRUNC | O_CREAT | O_NOCTTY | O_EXCL);
> flags |= O_RDONLY;
> f = dentry_open(&file->f_path, flags, file->f_cred);
> if (IS_ERR(f)) {
>
next prev parent reply other threads:[~2018-11-27 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 16:38 [PATCH] IMA: Mask O_RDWR if FMODE_READ is set Goldwyn Rodrigues
2018-11-27 12:05 ` Mimi Zohar [this message]
2018-11-27 14:06 ` Amir Goldstein
2018-11-27 14:14 ` Dmitry Vyukov
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=1543320309.3902.137.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=amir73il@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=rgoldwyn@suse.de \
--cc=syzbot+ae82084b07d0297e566b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zohar@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).