Hello,
On 2016년 05월 28일 07:44, Casey Schaufler wrote:
> On 5/27/2016 1:24 PM, Al Viro wrote:
>> On Fri, May 27, 2016 at 12:48:23PM -0700, Linus Torvalds wrote:
>>> On Fri, May 27, 2016 at 12:43 PM, Al Viro wrote:
Amended and force-pushed...
>>> Ok, I'll ignore that
Hello,
On 2016년 05월 28일 07:44, Casey Schaufler wrote:
> On 5/27/2016 1:24 PM, Al Viro wrote:
>> On Fri, May 27, 2016 at 12:48:23PM -0700, Linus Torvalds wrote:
>>> On Fri, May 27, 2016 at 12:43 PM, Al Viro wrote:
Amended and force-pushed...
>>> Ok, I'll ignore that branch for now, in the
On 5/27/2016 1:24 PM, Al Viro wrote:
> On Fri, May 27, 2016 at 12:48:23PM -0700, Linus Torvalds wrote:
>> On Fri, May 27, 2016 at 12:43 PM, Al Viro wrote:
>>> Amended and force-pushed...
>> Ok, I'll ignore that branch for now, in the hopes that there will be
>> actual
On 5/27/2016 1:24 PM, Al Viro wrote:
> On Fri, May 27, 2016 at 12:48:23PM -0700, Linus Torvalds wrote:
>> On Fri, May 27, 2016 at 12:43 PM, Al Viro wrote:
>>> Amended and force-pushed...
>> Ok, I'll ignore that branch for now, in the hopes that there will be
>> actual testing success. Please send
On Fri, May 27, 2016 at 12:48:23PM -0700, Linus Torvalds wrote:
> On Fri, May 27, 2016 at 12:43 PM, Al Viro wrote:
> >
> > Amended and force-pushed...
>
> Ok, I'll ignore that branch for now, in the hopes that there will be
> actual testing success. Please send a full
On Fri, May 27, 2016 at 12:48:23PM -0700, Linus Torvalds wrote:
> On Fri, May 27, 2016 at 12:43 PM, Al Viro wrote:
> >
> > Amended and force-pushed...
>
> Ok, I'll ignore that branch for now, in the hopes that there will be
> actual testing success. Please send a full pull request at that point,
On Fri, May 27, 2016 at 12:43 PM, Al Viro wrote:
>
> Amended and force-pushed...
Ok, I'll ignore that branch for now, in the hopes that there will be
actual testing success. Please send a full pull request at that point,
ok?
Linus
On Fri, May 27, 2016 at 12:43 PM, Al Viro wrote:
>
> Amended and force-pushed...
Ok, I'll ignore that branch for now, in the hopes that there will be
actual testing success. Please send a full pull request at that point,
ok?
Linus
On Fri, May 27, 2016 at 12:34:34PM -0700, Linus Torvalds wrote:
> On Fri, May 27, 2016 at 12:26 PM, Al Viro wrote:
> >
> > Umm... Would something along the lines of [...]
>
> Sure. That makes me go "ahh, ok, I see why".
Amended and force-pushed...
On Fri, May 27, 2016 at 12:34:34PM -0700, Linus Torvalds wrote:
> On Fri, May 27, 2016 at 12:26 PM, Al Viro wrote:
> >
> > Umm... Would something along the lines of [...]
>
> Sure. That makes me go "ahh, ok, I see why".
Amended and force-pushed...
On Fri, May 27, 2016 at 12:03:37PM -0700, Casey Schaufler wrote:
> I haven't actually seen the problem, but I've been having
> real trouble getting a systemd configuration working properly.
> The quickest validation will probably be coming from Seung-Woo Kim,
> who reported the issue initially. I
On Fri, May 27, 2016 at 12:03:37PM -0700, Casey Schaufler wrote:
> I haven't actually seen the problem, but I've been having
> real trouble getting a systemd configuration working properly.
> The quickest validation will probably be coming from Seung-Woo Kim,
> who reported the issue initially. I
On Fri, May 27, 2016 at 12:26 PM, Al Viro wrote:
>
> Umm... Would something along the lines of [...]
Sure. That makes me go "ahh, ok, I see why".
Linus
On Fri, May 27, 2016 at 12:26 PM, Al Viro wrote:
>
> Umm... Would something along the lines of [...]
Sure. That makes me go "ahh, ok, I see why".
Linus
On Fri, May 27, 2016 at 12:01:05PM -0700, Linus Torvalds wrote:
> Al, if you want Casey to help test, I think you should write out the
> full git repository address, rather than just say "See
> vfs.git#smack-fix".
>
> Anybody who isn't used to pulling for you will just wonder where you
> keep
On Fri, May 27, 2016 at 12:01:05PM -0700, Linus Torvalds wrote:
> Al, if you want Casey to help test, I think you should write out the
> full git repository address, rather than just say "See
> vfs.git#smack-fix".
>
> Anybody who isn't used to pulling for you will just wonder where you
> keep
On 5/27/2016 11:51 AM, Al Viro wrote:
> On Fri, May 27, 2016 at 04:11:41PM +0100, Al Viro wrote:
>
>>> After commit, "b968091 security_d_instantiate(): move to the point prior to
>>> attaching dentry to inode", booting on system with
>>> systemd and security smack, following kernel panic occurs.
On 5/27/2016 11:51 AM, Al Viro wrote:
> On Fri, May 27, 2016 at 04:11:41PM +0100, Al Viro wrote:
>
>>> After commit, "b968091 security_d_instantiate(): move to the point prior to
>>> attaching dentry to inode", booting on system with
>>> systemd and security smack, following kernel panic occurs.
On Fri, May 27, 2016 at 11:51 AM, Al Viro wrote:
> On Fri, May 27, 2016 at 04:11:41PM +0100, Al Viro wrote:
>> There is a fairly straightforward way to handle that - do to ->setxattr()
>> what we'd already done to ->getxattr(). See vfs.git#smack-fix. Warning:
>> it's
On Fri, May 27, 2016 at 11:51 AM, Al Viro wrote:
> On Fri, May 27, 2016 at 04:11:41PM +0100, Al Viro wrote:
>> There is a fairly straightforward way to handle that - do to ->setxattr()
>> what we'd already done to ->getxattr(). See vfs.git#smack-fix. Warning:
>> it's only build-tested. I'm
On Fri, May 27, 2016 at 04:11:41PM +0100, Al Viro wrote:
> > After commit, "b968091 security_d_instantiate(): move to the point prior to
> > attaching dentry to inode", booting on system with
> > systemd and security smack, following kernel panic occurs.
>
> /*
>
On Fri, May 27, 2016 at 04:11:41PM +0100, Al Viro wrote:
> > After commit, "b968091 security_d_instantiate(): move to the point prior to
> > attaching dentry to inode", booting on system with
> > systemd and security smack, following kernel panic occurs.
>
> /*
>
On Fri, May 27, 2016 at 08:09:09PM +0900, Seung-Woo Kim wrote:
> After commit, "b968091 security_d_instantiate(): move to the point prior to
> attaching dentry to inode", booting on system with
> systemd and security smack, following kernel panic occurs.
/*
On Fri, May 27, 2016 at 08:09:09PM +0900, Seung-Woo Kim wrote:
> After commit, "b968091 security_d_instantiate(): move to the point prior to
> attaching dentry to inode", booting on system with
> systemd and security smack, following kernel panic occurs.
/*
Hello,
After commit, "b968091 security_d_instantiate(): move to the point prior to
attaching dentry to inode", booting on system with
systemd and security smack, following kernel panic occurs.
---
Unable to handle kernel paging request at virtual address fff4
pgd = eda74000
[fff4]
Hello,
After commit, "b968091 security_d_instantiate(): move to the point prior to
attaching dentry to inode", booting on system with
systemd and security smack, following kernel panic occurs.
---
Unable to handle kernel paging request at virtual address fff4
pgd = eda74000
[fff4]
26 matches
Mail list logo