From: Christian Brauner <brauner@kernel.org>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
Linus Torvalds <torvalds@linuxfoundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ptikhomirov@virtuozzo.com, Andrey Ryabinin <arbn@yandex-team.com>
Subject: Re: [PATCH] fs/coredump: open coredump file in O_WRONLY instead of O_RDWR
Date: Tue, 16 May 2023 15:46:11 +0200 [thread overview]
Message-ID: <20230516-melancholisch-traten-3336ff6e9d30@brauner> (raw)
In-Reply-To: <CAHk-=wjex4GE-HXFNPzi+xE+w2hkZTQrACgAaScNdf-8hnMHKA@mail.gmail.com>
On Thu, 20 Apr 2023 15:04:09 +0300, Vladimir Sementsov-Ogievskiy wrote:
> This makes it possible to make stricter apparmor profile and don't
> allow the program to read any coredump in the system.
>
>
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] fs/coredump: open coredump file in O_WRONLY instead of O_RDWR
https://git.kernel.org/vfs/vfs/c/f84566e710af
next prev parent reply other threads:[~2023-05-16 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 12:04 Vladimir Sementsov-Ogievskiy
2023-05-10 15:15 ` Vladimir Sementsov-Ogievskiy
2023-05-15 17:55 ` Christian Brauner
2023-05-15 18:50 ` Linus Torvalds
2023-05-15 19:13 ` Linus Torvalds
2023-05-16 8:05 ` Vladimir Sementsov-Ogievskiy
2023-05-16 13:46 ` Christian Brauner [this message]
2023-05-16 13:47 ` Christian Brauner
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=20230516-melancholisch-traten-3336ff6e9d30@brauner \
--to=brauner@kernel.org \
--cc=arbn@yandex-team.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=torvalds@linuxfoundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=vsementsov@yandex-team.ru \
/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
all inboxes | Powered by JetHome®